Authentication
All Open Fabric APIs use an OAuth 2.0 access token (Bearer token) for authentication.
All Open Fabric APIs use an OAuth 2.0 access token (Bearer token) for authentication.
Open Fabric provides two environments for integration:
When an API request fails, Open Fabric returns an HTTP error status code. Depending on the endpoint, the response body may also include an error code and message.
Create operations (for example: transactions, refunds, and chargebacks) support idempotency. Idempotency lets you safely retry a request without accidentally performing the same operation twice.
This section covers the foundations you need to integrate with Open Fabric APIs.
Open Fabric APIs follow REST conventions and use standard HTTP verbs and status codes.
Our notification systems send you real-time updates to your systems as they get generated. Open Fabric expects all notifications to be acknowledged with a 2xx HTTP Status Code and in the absence of which we will retry the notification.
Reporting APIs
Open Fabric provides access to several SDKs and Reference Apps for our Account tokenization products, specifically for Own App tokens and Digital Wallet Tokens. Please work with our commercial teams and align on the delivery schedules.
Plan for testing across environments. Because we are directly integrated with payment networks (such as Mastercard and Visa), we validate that integrated systems can handle an extensive set of network-defined test cases.