Payment

Initiate a debit transaction.

Certain parameters are required for specific payment methods and certain parameters act differently depending on the payment method.

• For 1Voucher, customer.mobile (the customer's phone number for receiving change vouchers and refunds) and virtualAccount.password (the voucher PIN) are required.
• For M-PESA, virtualAccount.accountId (the customer's 12-digit phone number) and shopperResultUrl are required. M-PESA only accepts integer amounts, not decimals, so round up your amount.
• For blink by Emtel and MCB Juice, virtualAccount.accountId (the customer's 8-digit phone number) and shopperResultUrl are required.
• For Mobicred, virtualAccount.accountId (the customer's Mobicred email address), virtualAccount.password (the customer's Mobicred password), and shopperResultUrl are required.
• For Capitec Pay, virtualAccount.type (the customer's identifier type; IDNUMBER, CELLPHONE, or ACCOUNTNUMBER), virtualAccount.accountId (the customer's 13-digit ID number, 10-digit phone number starting with 0, or up-to 64-digit, alphanumeric bank account number), and shopperResultUrl are required. High-risk merchants must provide the verified IDNUMBER and cannot use the CELLPHONE or ACCOUNTNUMBER account types.
• For RCS cards, card.number (the customer's RCS card number) and shopperResultUrl are required.
• For PayShap, virtualAccount.bank (the customer's bank; DISCOVERYBANK, NEDBANK, or TYMEBANK), virtualAccount.type (the customer's identifier type; CELLPHONE), virtualAccount.accountId (the customer's phone number in the +27-123456789 format), and shopperResultUrl are required.
• For Payflex, ZeroPay, Scan to Pay, Peach EFT, Float, Happy Pay, MoneyBadger, and MauCAS the shopperResultUrl is required.

For more information, see the documentation and for sample calls, see our public Postman collection.