Merchant / gateway integration guides
This section contains the reference documentation for merchants and payment gateways that integrate with Open Fabric to offer your payment method at checkout.
If you’re the payment method integrating with Open Fabric, start with the Orchestrated integration guide. You can then share the relevant guide below with each merchant or gateway you onboard.
Why Open Fabric simplifies integrations
Without Open Fabric, a merchant/gateway typically needs to build and operate a custom integration per payment method, including settlement/reconciliation changes and back-office tooling.
With Open Fabric:
- The merchant/gateway integrates once with Open Fabric.
- For each approved transaction, Open Fabric provides a one-time card-based payment credential.
- The merchant/gateway processes it using their existing card infrastructure (and can refund via their existing card flow).
Handover patterns
Merchants/gateways choose one of two patterns depending on PCI scope and payment gateway capabilities.
| Card handover | PG token handover | |
|---|---|---|
| Experience |  |  |
| Best for | Payment gateways and PCI-compliant merchants who can fetch and handle card details server-side. | Merchants that are not PCI compliant and want Open Fabric to tokenize the card with their payment gateway. |
| Guide | Card handover | PG token handover |
API-only integration guides (no Web SDK)
Some gateways/merchants prefer a direct API integration for finer-grained control. Use these guides: