In order to minimize your burden of PCI DSS compliance, you should not let payment card data be stored or transmitted through your servers. The best way to minimize the burden while maximizing the customizability is using an iframe-based solution that already is integrated with our payment tokens API.
We call this solution FramePay.
You will need your publishable key for use with FramePay. It's very important not to use your secret key, as the key will reside within the client browser.
A payment token can be created for any kind of payment method, even if there are no special inputs required.
Payment cards and bank accounts require special inputs such as the card number or bank account number.
You can see more in the FramePay docs.
The payment token will be supplied to the surrounding order form, and the value (the token id) will be used in the next API request.
Use the form below to test FramePay by providing a publishable API key from your sandbox account.
You may make up fictitious data to complete this stage of the tutorial:
- the customer's billing address
- the payment instrument values depending on the type (credit card or bank account)... for the tutorial, use
4111 1111 1111 1111with any future expiration and any 3 digit cvv.
See the FramePay Getting Started Guide for the step by step procedure to use FramePay in your forms.
After you submit the form, you should receive a token. Copy that down, as you'll need it to complete the next step.