2023-02-14

Features

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

📘

The following parameters are mandatory:

• virtualAccount.type: The customer's identifier type; either CELLPHONE or IDNUMBER.
• virtualAccount.accountId: The customer's 11-digit phone number or 13-digit ID number.

2022-12-20

Features

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.

2022-12-05

Features

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.

2022-11-01

Features

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

📘

For 1Voucher, the following parameters are mandatory:

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

For more information, see the Postman collection.

2022-09-30

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.

Features

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, Mobicred, Scan to Pay, Apple Pay, 1Voucher, and M-PESA. 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.

Support

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