If you have an existing Android Components integration, you can use our Redirect Component to redirect the shopper to the KNET app or website where they can complete the payment.
When making an KNET payment, you need to:
Before you begin
This page explains how to add KNET to your existing Android Components integration. The Android Components integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Components integration guide.
Before starting your KNET integration:
- Make sure that you have set up your back end implementation for making API requests.
- Add KNET in your test Customer Area.
Show KNET in your payment form
Include KNET in the list of available payment methods. You don't need to collect any information from the shopper in your payment form.
Specify in your /paymentMethods request:
The response contains
We provide logos for KNET which you can use on your payment form. For more information, refer to Downloading logos.
Make a payment
When the shopper proceeds to pay, you need to:
From your server, make a /payments request, specifying:
paymentMethod.type: Set this to knet.
- shopperName: The shopper's full name.
- shopperEmail: The shopper's email address.
- telephoneNumber: The shopper's telephone number.
returnUrl: URL to where the shopper should be redirected back to after they complete the payment. Get this URL from the Component in the
The /payments response contains an
actionobject with the information needed to redirect the shopper.
- Pass the
actionobject to your client app.
Handle the redirect
Use the Redirect Component to redirect the shopper to KNET.
After the shopper returns to your app, make a POST /payments/details request from your server, providing:
actionComponentData.detailsobject from the Redirect Component.
You receive a response containing:
resultCode: Use this to present the payment result to your shopper.
pspReference: Our unique identifier for the transaction.
Present the payment result
resultCode values you can receive for KNET are:
|resultCode||Description||Action to take|
|Authorised||The payment was successful.||Inform the shopper that the payment has been successful.|
|Cancelled||The shopper cancelled the payment while on KNET's website.||Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.|
|Error||There was an error when the payment was being processed.||Inform the shopper that there was an error processing their payment. The response contains a
|The shopper has completed the payment but the final result is not yet known.||Inform the shopper that you've received their order, and are waiting for the payment to be completed.
To know the final result of the payment, wait for the AUTHORISATION webhook.
|Refused||The payment was refused by the KNET.||Ask the shopper to try the payment again using a different payment method.|
|eventCode||success field||Description||Action to take|
|AUTHORISATION||false||The transaction failed.||Cancel the order and inform the shopper that the payment failed.|
|AUTHORISATION||true||The shopper successfully completed the payment.||Inform the shopper that the payment has been successful and proceed with the order.|
|OFFER_CLOSED||true||The shopper did not complete the payment.||Cancel the order and inform the shopper that the payment timed out.|
Test and go live
To test KNET payments, use the test card details provided by Tap.
Before you can accept live KNET payments, you need to submit a request for KNET in your live Customer Area.