Secure Payments API – Payment Profiles

Payment Profiles

In order to process any payments with Secure Payments (formerly PCI Wallet), you need to add some credit cards and/or checking accounts to your Secure Payments account.

Since credit card information is highly sensitive and subject to PCI compliance, an HTML iframe is provided.

When integrating with Secure Payments, it’s fundamental that credit cards are added to your profile through the iframe only. Otherwise your software will be subject to PCI compliance.

Credit cards are tokenized. It is never returned to you in any way (even encrypted). Tokens are not saved in Secure Payments, and there’s no way to retrieve them if lost.

When a credit card is saved in Secure Payments, a corresponding token is generated and returned to you (see Creating a Credit Card). This token represents your credit card stored in Secure Payments, and its safe to save it within your own application. Endpoints to process a payment with a credit card will require you to send the corresponding credit card token.

If a token is lost, it cannot be retrieved from Secure Payments as they are never saved on our side. After a period of inactivity, the corresponding credit card information will be deleted automatically.

Payment profile options include:

How did we do?

Powered by HelpDocs (opens in a new tab)