Release notes


This release of the Payments API adds support for Nedbank Direct EFT.


This release of the Payments API removes support for InstantEFT.


This release of the Payments API updates Capitec Pay as follows:

  • Added the ability for the customers of low-risk merchants to pay using their phone number, in addition to the already-supported ID number.
  • High-risk merchants, as determined by Capitec, must provide verified ID numbers in requests to Peach Payments to enable their customers to pay using Capitec Pay. The customers of high-risk merchants cannot pay using phone numbers.


This release of the Payments API adds support for Capitec Pay.


The following parameters are mandatory:

  • virtualAccount.type: The customer's identifier type; must be IDNUMBER.
  • virtualAccount.accountId: The customer's 13-digit ID number.


This release of the Payments API adds support for Mobicred in South Africa.


The virtualAccount.accountId (the customer's Mobicred email address) and virtualAccount.password (the customer's Mobicred password) parameters are mandatory.


This release of the Payments API adds support for Scan to Pay, M-PESA, and blink by Emtel.


  • For M-PESA, the virtualAccount.accountId parameter (the customer's 12-digit phone number) is mandatory.
  • For blink by Emtel, the virtualAccount.accountId parameter (the customer's 8-digit phone number) is mandatory.


This release of the Payments API adds support for 1Voucher.


For 1Voucher, the following parameters are mandatory:

  • The customer's phone number for receiving change vouchers and refunds.
  • virtualAccount.password: The voucher PIN.

For more information, see the Postman collection.


Peach Payments is proud to announce the limited availability release of the Payments API to a subset of merchants. The Payments API introduces a range of new payment methods that were available on the Checkout product.


The Payments API offers the following features:

  • Easier to integrate with, offers much better performance, and supports more transactions per second than the old payments API.
  • Support for a range of new payment methods to help expand your target market, increase basket size, and improve payment conversions:
    • InstantEFT
    • Payflex
    • ZeroPay
    • FinChoicePay


The Payments API also supports EFTsecure.

Known limitations

The Payments API does not support card, A+ store cards, Apple Pay, and PayPal. Checkout supports these payment methods.

Upgrade guide and considerations

The Payments API is backwards-compatible with the previous payments API.

To upgrade, follow the instructions on the Upgrade guide page.


If any issues occur with the Payments API, contact support.