_Docs/
Get StartedModulesPlatformDeployCookbookChangelogReference
_Deploy
  • Deployment Overview
    • Overview
    • Requirements
    • Demo
      • All-in-one Demo Chart
    • Installation
      • Operator Setup
      • Control Plane SetupEE
    • Infrastructure Services
      • PostgreSQL
      • Message Broker
      • Temporal
    • Module Configuration
      • Stack Configuration
      • Gateway Module
      • Ledger Module
      • Payments Module
      • Auth ModuleEE
      • Orchestration ModuleEE
      • Reconciliation ModuleEE
      • Wallets ModuleEE
      • Webhooks ModuleEE
    • Configuration Reference
      • Operator settings reference
      • API Reference
    • Backups management
    • Troubleshooting
    • Configure OpenTelemetry
    • Traces
    • Metrics
    • Upgrade from the operator
    • Database update
  1. Deploy
  2. Self-Hosted
  3. Module Configuration
  4. Payments Module
Deploy

Payments Module

This page requires self-hosted edition.
Deployment

Formance Payments is a unified API that abstracts over multiple different payment providers like Stripe and Wise, simplifying the process of building money flows that stitch multiple payment providers together.

Requirements#

Formance Payments requires:

  • PostgreSQL: See configuration guide here.
  • Temporal: See configuration guide here.
  • (Optional) Broker: See configuration guide here.

Setting up Temporal#

Temporal is a required dependency for Formance Payments. The easiest way to set up Temporal with Payments is to use the docker-compose configuration provided in the payments repository, which includes all necessary services:

  • temporal and temporal-worker
  • postgres
  • payments-migrate
  • payments-worker
  • payments

The docker-compose file in the main stack repository does not include the complete Temporal setup. Make sure to use the configuration from the payments repository instead.

Alternative: Payments without Temporal#

If you don't need the latest Payments features and prefer not to manage Temporal infrastructure, you can use an earlier version of Payments that doesn't require Temporal while providing similar core functionality.

Payments Object#

You can find all the available parameters in the comprehensive CRD documentation.

YAML
apiVersion: formance.com/v1beta1
kind: Payments
metadata:
  name: formance-dev
spec:
  stack: formance-dev
Ledger ModuleAuth Module
On This Page
  • Requirements
  • Setting up Temporal
  • Alternative: Payments without Temporal
  • Payments Object