Reccuring Payment Orchestration

For recurring payments, merchants can initiate Direct Debit transactions using a customer's previously bound bank account without requiring OTP verification for each payment, provided the Non-OTP flow has been approved by Ayoconnect.

Merchants can manage their own billing schedules and initiate payments using the payment-host-to-host API.

Payment Status Handling

• SUCCESS: Mark the payment as successful.
• PENDING: Keep the payment in a processing state until the final status is received.
• HTTP 5xx or timeout: Do not immediately mark the payment as failed or retry the transaction. Wait for the callback or use the /debit/status API to confirm the transaction outcome.
• FAILED: Merchants may initiate a new payment attempt, subject to the applicable failure reason and bank restrictions.
• NOT FOUND: Merchants may initiate a new payment attempt once it is confirmed that the original transaction was never successfully initiated.

Payment Retry Behavior

Once a transaction is confirmed as FAILED, merchants can:

1. Retry using the same bound account: Initiate another payment using the customer's existing account token.
2. Retry using another bound account: Initiate payment using another active bank account previously bound by the customer, provided it is eligible and authorized for the payment.

Merchants should ensure that only one payment attempt is actively processing for the same billing obligation to prevent duplicate charges.

Important: A 5xx response does not necessarily indicate payment failure. Always verify the final transaction status before initiating another payment attempt.