Direct Debit Payment

The Direct Debit Payment feature (Direct Debit Payment API) can be utilized after binding has been done.

Through this feature, merchants can:

1. Initiate a payment on behalf of your customer, directly deducting their binded bank account
2. Choose to request OTP from customer to confirm payment, or a non-OTP flow (i.e. recurring payments without customer intervention)

After a payment attempt, a callback will also be sent to the partner's charge payment URL with the status of the payment. The structure of the callback is mentioned in the Callback section of the Direct Debit Payment API.

Payment Status

Possible payment statuses are:

1. SUCCESS
   1. This indicates definitive success from the bank
2. INITIATED
   1. This indicates that the transaction has not reached a final state from the bank
3. PROCESSING
   1. This indicates that the transaction has not reached a final state from the bank
4. PENDING_USER_VERIFICATION
   1. This status is returned if an OTP verification is still pending for OTP-based non-Danamon payments
5. PENDING_USER_VERIFICATION WITH URL
   1. This status is specific for OTP-based payments through Danamon. This status does not apply to any other banks, and neither does it apply to non-OTP based payments through Danamon
6. TIMEOUT
   1. This indicates that the transaction has not reached a final state from the bank due to a timeout on the bank side
7. FAILED
   1. This status indicates definite failure from the bank

Limitations

Please note the following limitations:

• OTP & Non-OTP flows are approved on case-by-case basis, specifically as part of a merchant's onboarding process through Ayoconnect. Our APIs only allows merchants to select between these 2 flows once they have been approved for both by Ayoconnect