Our in-store transactions APIs allow you to create a new purchase, refund or a cancel request for the in-store transactions on the Wpay platform. All APIs are IP restricted and require accepted authentication mechanism as listed below within the Encryption section of the document to make successful API requests.
Becoming a Partner
To become a partner, please contact us to find out how to get set up as a Wpay payment partner. Once you have been set up as a partner, following items are required before you can go live:
Client Certificate: The client certificate is used to establish mTLS connections with our infrastructure
API Credentials:. These are used to sign your HTTP requests
BDK: AES DUKPT encryption key required for PIN block translation.
API: Integration You will integrate with our APIs
QA/UAT: We will validate your implementation and once validation has concluded you are ready to go live.
Security
Following security protocols are required to make a successful API call to the Wpay payment platform.
| Encryption Type | Description |
|---|---|
| mTLS | Client Certificate generated by Wpay |
| BDK | Required for AES DKPUT to generate PIN BLOCK encryption. |
| HMAC Keys | Required to generate a HMAC. |