B2B Payment API
End-to-end-encryption (e2ee) helps to ensure that sensitive data remains unreadable in as many locations as possible. Primarily card data (credit and debit) and other sensitive data points fall into this category.
In contrast to earlier API versions, all data points noted as e2ee are required to be encrypted before being sent to this API.
The following endpoints will enable you to accomplish this via code.
Provides the public key side of the asymmetric encryption, needed for the actual endpoints requiring e2ee, as well as the following test endpoint.
If you receive a successful/expected response from this endpoint, you should never encounter an encryption/decryption error on the endpoints that require it.
If implementing your own e2ee client, it is advised to make sure your calls pass on this endpoint before calling the "real" ones.
Creating the value manually, using CLI tools:
Testing the value manually, using CLI tools: At this point, you can manually inspect the value (), or put it into your HTTP client of choice, or use the Try It Out button as part of this documentation.
If all is well, you should see a True response (if not, you will see an error).
Common errors Ensure you are using the correct padding (RSA-OAEP) and correct encoding (base64, NOT base64 url encoded).
Loading...