Transaction Processing
If you don't use our Credit Core or our Authorizer, you will need to implement and expose the "Authorization" and "Adjustments" endpoints in your backend so we can communicate.
When We Consume Your Endpoints
- During online flow: Every time a user uses their card in any store or e-commerce
- Network reconciliation: When the network (Mastercard, Visa, etc) requests reconciliation of all payments presented by merchants
Important Considerations
- Reconciliation differences: If there is a difference in reconciliation, we will request an adjustment to your API
- Response time: We will need your endpoints to respond as quickly as possible to ensure a good user experience. If the response is delayed, we will reject the transaction
- Idempotency: We will use an idempotency header to avoid creating two or more resources for the same request
- Validation and signature: You will need to validate and sign authorizations following the steps in this documentation
How to Test Your Implementation
You can test your backend implementation with some typical operations we will send with a Postman collection included in our public examples repository.
You can import the collection into a Postman instance and simulate real requests to your backend, including the signature generation and verification algorithm.
Reconciliation Files
Daily we will send you two files in CSV format via SFTP (Secure File Transfer Protocol) so you can reconcile all transactions between your system and ours.