Payment initiation
Create a payment request with a consistent business reference and the required payer context.
Pay-ins
Make every incoming payment easier to follow and operate.
Create collection experiences that connect payment initiation, customer instructions, status updates, exceptions, refunds and reconciliation into one traceable flow.
Pay-ins
More than a payment request
Give customer-facing and operations teams the information they need at each stage of the collection journey.
Method presentation
Present eligible methods and currencies according to the agreed market and customer flow.
Status updates
Use synchronous responses and asynchronous events to keep internal systems aligned.
Operational review
Route pending, rejected or unusual transactions into a clear follow-up process.
Refund handling
Link full or partial refund actions to the original transaction and its audit trail.
Reconciliation
Compare references, amounts, fees and outcomes through structured reports or exports.
Lifecycle visibility
Know what happened after the customer clicked pay.
Pending and failed outcomes require clear action, not guesswork. Transaction timelines can give support and finance teams a common view of updates, retries, reversals and final outcomes.
- Unique merchant references
- Pending and final status separation
- Duplicate request protection
- Refund and reversal linkage
Payment infrastructure for financial businesses
A typical pay-in flow
-
Create
Your platform sends the amount, currency, customer context and unique reference.
-
Complete
The payer follows the eligible method journey and receives a clear result.
-
Confirm
Status events update your product and operational records for follow-up and reconciliation.
Questions
Answers for planning your next step.
The exact implementation depends on your business, market and onboarding requirements.
Can pay-ins support more than one payment method?
The integration model can support multiple method types. Actual methods are confirmed by market, partner and onboarding eligibility.
How are duplicate requests handled?
The intended API design uses merchant references and idempotency controls so retried requests do not create unintended duplicate transactions.
Build the right payment flow
Ready to simplify how funds move through your business?
Tell us about your markets, transaction flows and integration priorities. We will help you shape a practical solution scope.