Guidelines for test transactions

Follow

To make sure that your payment gateway works perfect when you start doing live transactions we require to do a couple of test transactions in the sandbox that was setup for you.

There are 3 requirements for the test transactions (see below for a broader explanation on these)

  • Test all the payment flows that you are planning to use
  • Provide all relevant parameters with the transaction
  • Do transactions with different test cards

 

Example from the BIP of correctly setup transactions for a payment flow with stored cards. Note that the Recurring channel is called 'PP01 Nedbank' here.

Test all the payment flows that you are planning to use

The quick reference card below describes the highlights for each flow in case you are doing a Custom Integration. The highlights below are not relevant for WooCommerce or Magento integrations. The full documentation here describes the complete Custom setup in further detail.

 

Copy and Pay and MSDK

Server-to-Server

Once off (DB)

Channel (entityID): 3DS
Post to: https://test.oppwa.com/v1/payments/

Channel (entityID): 3DS
Post to: https://test.oppwa.com/v1/payments/

Checkout + card storage (DB.RG)

Channel (entityID): 3DS
createRegistration=true
recurringType=INITIAL

Channel (entityID): 3DS
createRegistration=true
recurringType=INITIAL​
Handle 3DS redirect manually (async)

Add card (PA) - standalone storage

Channel (entityID): 3DS
createRegistration=true
amount=1.00
paymentType=PA
recurringType=INITIAL

recurringType=INITIAL
createRegistration=true
amount=1.00
paymentType=PA
Handle 3DS redirect manually (async)
Channel (entityID): 3DS

Subscription - Recurring

Channel (entityID): 3DSrecurringType=REPEATED
Post to: https://test.oppwa.com/v1/registrations/{id}/payments

Channel (entityID): Recur
recurringType=REPEATED
Post to https://test.oppwa.com/v1/registrations/{id}\

3DS Single click

Channel (entityID): 3DS
registrations[n].id=XXXXXXXXXXXXXX

Channel (entityID): 3DS
recurringType=REPEATED
Post to https://test.oppwa.com/v1/registrations/{id}\
Handle 3DS redirect manually (async)

No 3DS Single click

Channel (entityID): 3DS
recurringType=REGISTRATION_BASED
registrations[n].id=XXXXXXXXXXXXXX

Channel (entityID): Recur recurringType=REPEATED
Post to https://test.oppwa.com/v1/registrations/{id}\

 

Provide all relevant parameters with the transaction

Our online documentation for Copy and Pay demonstrates the minimum requirements for transacting on our platform.

However there is additional customer data we highly recommend that you include in the Prepare CheckoutID request. These additional data items are required for various processes including reconciliation and risk management.

You can access the complete list of available parameters here:

Peach Payments REST API Reference

Please include the following parameters in your checkoutid request.

These are added in the same way as the other parameters such as Currency and Amount that are currently being sent.

merchantTransactionId

customer.givenName
customer.surname

customer.email

shipping.street1 
shipping.street2
shipping.city
shipping.state
shipping.postcode
shipping.country

Optional to include:

customer.mobile

Notes:
1. The merchantTransactionId is simply the order ID from your shopping cart / order management system. This will help you connect payments in the Peach system with orders in your system.

2. Please use the country code ZA for South Africa. 

 

Do transactions with different test cards

You can find the test cards here

The 4111 1111 1111 1111 and the 4242 4242 4242 4242 card should provide successful transactions.

 

Have more questions? Submit a request

Comments

Powered by Zendesk