Payment Method Tokenization

Tokenization is the process of replacing sensitive data with unique identification symbols that retain all the essential information about the data without compromising its security.

The Ansa platform does not directly access or handle any payment data. Instead, Ansa integrates with various tokenization services offered by third-party vendors and payment service providers to securely handle the payment data.

📘

Let's discuss the appropriate tokenization strategy for protecting payment data

Feel free to reach out to Ansa to discuss proper tokenization strategy that is tailored to your system and Ansa integration.

Payment service provider tokenization

Payment service providers often offer tokenization features to collect sensitive card or bank account details, or personally identifiable information (PII).

Square provides tokenization features on various payment resources. Ansa recommends that merchants use Square-provided SDKs, such as the web SDK and mobile SDKs, to securely handle payment data.

Stripe also provides tokenization features on different payment resources. We recommend that merchants use Stripe's integration guides to help setup secure collection of customer's payment data. Ansa recommends using the Stripe SetupIntent flow with either the Card Element or the Payment Element to collect payment information for future use.

Third party tokenization service provider

Merchants can use third-party tokenization services that are PCI DSS compliant to securely collect and forward payment data to payment service providers. Ansa integrates with third-party tokenization services and payment service providers to use tokens that have been created, without directly accessing any sensitive data.

Using raw card data with Ansa

Ansa enables customers to use raw card data to create an Ansa payment method. This raw card data is securely routed through a PCI DSS compliant tokenization service to a payment service provider.

Here are a few simple steps to create an Ansa payment method with raw card data.

First, merchants can decide which URL to route card data to, depending on the environment. For development purposes in the sandbox environment, use https://secure-sandbox.getansa.com. For the production environment, use https://secure.getansa.com.

Secondly, if you are using the sandbox mode, you can choose different test cards based on your payment service provider's configurations. For instance, if your Ansa merchant is integrated with Stripe, please refer to the Stripe testing documentation for test cards. If your Ansa merchant is integrated with Square, refer to Square sandbox payments. In a production environment, you should use real card data.

Third, use the create payment method with card data API to create an Ansa payment method. Afterward, you can use the created Ansa payment method ID with the add balance API.

Using linked bank accounts from Plaid

📘

Don't use Plaid? Let's find an appropriate alternative for you.

Feel free to reach out to Ansa to discuss an alternative for verifying bank accounts, assessing risk, and enabling A2A funding.

If your account is configured with Plaid, you can use your users' linked bank accounts as Ansa payment methods.

When using Plaid Link , your application will receive public tokens from Plaid's SDK corresponding to the bank accounts that the user has connected. You will need to exchange these public tokens for a longer-lived access token, and then create a processor token from the access token using ansa as the processor value.

You can pass these processor tokens into the Create Payment Method with Payment Token API to create an Ansa payment method for each one. Afterward, you can use the created Ansa payment method ID with the Add Balance API as usual.

For help with configuring Plaid for your account, please reach out to your implementation manager.