Payment Requests
Making Payment Requests
Each payment operation uses a RequestMsg object. Below are examples for each type:
An API for making payment requests is a set of programmable interfaces that allows a client application—such as a mobile app, ePOS system, or card terminal—to initiate and manage payment transactions with Payment Orchestration. Here's what it typically does:
What the SDK Does
1
Initiates Transaction Instance
It sends a structured request to Payment Orchestration to begin a transaction. This includes details like amount, currency and merchant ID
2
Handles Card Data
It securely transmits card information (PAN, expiry, CVV) or tokenised data, often using encryption or PCI-compliant methods.
3
Supports Multiple Payment Types
It can handle various transaction types such as Sale/Purchase, Pre-Auth, Capture, Reversal, Void
4
Manages Authentication
It may trigger PIN entry, Signature flows depending on the card type and transaction context.
5
Processes Responses
It receives and interprets the Payment Orchestration's response—approved, declined, or error—and passes it back to the client app for UI updates or receipt generation.
6
Logs and Audits
It often includes logging mechanisms for transaction tracking, reconciliation, and compliance reporting.
7
Supports Fallbacks and Retries
In case of failure, the API may support retry logic or “fall forward” mechanisms to alternate payment methods or gateways.
Sequence
On this page
- Payment Requests