How a DCB payment works
DCB uses an OTP opt-in for the first payment, then charges the saved opt-in:- The customer selects DCB at checkout and enters their mobile number.
- You authorize the payment. Payrails starts an opt-in with the PSP, and the PSP sends an OTP to the customer’s phone by SMS.
- The authorize response asks you to confirm the payment. You collect the OTP from the customer and send it in a confirm request.
- Payrails validates the OTP with the PSP, confirms the opt-in and charges the first payment to the customer’s carrier account.
- Payrails saves the opt-in as a payment instrument. For later payments, you authorize with that instrument and the customer doesn’t enter an OTP again.
Supported currencies and countries
DCB is available in the countries below. Charge each payment in the local currency of the customer’s carrier country.Integrate DCB
Choose the PSP that processes DCB for you. The guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.Boku
DCB via Boku
Check PSPs
Save Instruments and merchant-initiated transactions (MIT) work through the saved opt-in. The first DCB payment creates the opt-in, and Payrails charges later payments against it.Ways to integrate DCB
- Payrails SDK: the Web SDK shows DCB when your workflow returns it as a payment option.
- Payrails API: call lookup payment options, authorize with
dcbas thepaymentMethodCode, then confirm the first payment with the OTP. The PSP guide lists themetafields that PSP requires.