Direct Debit Binding

The Direct Debit Binding feature (registration-account-binding API) is the first process of the Direct Debit Journey of a user.

Binding in this context means registering the user's Bank Account in Ayoconnect's Direct Debit system so that payment can be made using that bank account.

It is a one-time process, and after a successful binding, the user can make payments as many times as they want as long as the card is not unbinded. If a bank account has unbinded, the user has to rebind it again.

Through this feature, you can:

• Bind a user's bank account to your product/service for recurring payments
• Define the bank name (BCA, BRI, Mandiri, etc) that the merchant would like to request user to bind

Bank Account Binding is done through Ayoconnect's webview. There are 2 steps a user would need to go through to ensure a successful binding process:

• User submits his bank account details
• User authenticates themselves

Once a bank account has been successfully binded, the user can be redirected to a merchant-specific URL, which must be provided during the merchant onboarding process. After that, new redirection URLs can be provided as parameters in the API but they will be applied only to that specific request.

Upon successful binding, Partners will receive accountToken via account binding callback. This token will not have any expiration from Ayoconnect side, but do note that banks will have their own Binding expiration time. See the table below

Binding Status

Possible latestBindingStatus statuses are:

1. IN_PROGRESS
   1. This indicates that the binding flow has been initiated but user has not submitted bank account details successfully, and thus has not reached the verification step
2. VERIFICATION_PENDING
   1. This indicates that the user has submitted his bank account details successfully, and is now at the authentication step (i.e. OTP verification step)
3. SUCCESS
   1. This indicates definitive successful binding from the bank
4. FAIL
   1. This status indicates definite binding failure status from the bank. You should initiate another binding attempt if you would like to try again
5. UNBINDED
   1. This status indicates that a previously binded bank account has been unbinded. This status will only be returned as part of the unbinding flow response

AccountToken Expiration from banks

If the user tries to bind an expired card, it will fail during binding process and will not be able to do payment. If user binds a valid card, and then in the future the card expires, payment attempts will fail. The payment charge API will return error "Card Expired"

User will need to re-bind with new card in order for partner to attempt another successful payment.

Rebinding behavior for each banks

If the user have successfully bind a valid card before on a merchant platform, and tries to bind the same card again on the same merchant platform, most banks will reject the binding request and return error message.

In this case, there are 2 options that the merchant can consider:

• Merchant need to unbind the card first before attempting to do another binding using the same card.
• Merchant can simply use the existing token to do payment without the need to do any binding.