Token Requestor Visa & Mastercard

Overview

Network tokenization through Visa Token Service and Mastercard Tokenization provides a secure method for processing payments without exposing sensitive card data. When a cardholder's credit card information is tokenized, the card networks generate a unique identifier (token) that replaces the actual card number, enhancing security while maintaining a seamless payment experience.

💡 Read more about tokenization in our blog post: Frisbii Blog

Key Benefits

• Enhanced Security: Tokens replace actual card numbers, reducing the risk of data breaches

• Automatic Card Updates: Frisbii automatically updates saved cards when issuers provide new card details

• Reduced Involuntary Churn: Customers don't need to manually update their payment information when cards are reissued

• Improved Authorization Rates: Network tokens typically have higher approval rates than traditional card numbers

Configuration

Setting Up Token Requestor IDs

To enable network tokenization in Frisbii Admin:

1. Navigate to your acquirer agreement settings via Configurations → Checkout management → Payment methods → Credit card agreement.
   

2. Open your acquirer agreement or create a new acquirer agreement if you don’t have one yet.

3. Locate the Token Requestor Configuration section.

4. For Visa and Mastercard, select your Token Requestor ID from the dropdown menu.

If you haven't created a Token Requestor ID yet:

4. Click Create Visa token requestor ID or Create Mastercard token requestor ID.

5. Follow the prompts to complete the setup.
   

These identifiers enable secure payment processing through network tokenization and allow Frisbii to automatically maintain your customers' payment methods.

👩‍💻 Test the setup

Testing the setup is not required. If you really want to test it, follow our technical documentation: Test payment method events

Webhook Events

👩‍💻 Technical Documentation

Find more information on webhook events in our technical documentation: Events

Once a card is tokenized, you'll receive webhook events to monitor changes to customer payment methods. Understanding and responding to these events is essential for maintaining a reliable payment process.

Available Events

customer_payment_method_updated

• When it occurs: The card network has provided updated card information from the issuing bank.

• What it means: The underlying card details have changed, such as a new card number (masked) or expiry date, but the token remains valid.

💡 Action required? No immediate action needed. The payment method is automatically updated and remains active. You may want to log this event for your records.

customer_payment_method_reactivated

• When it occurs: A previously failed or suspended payment method has been restored to active status.

• What it means: A temporarily suspended token has been resumed, or a previously failed card has been successfully retried.

💡 Action required? No immediate action needed, but you may want to notify the customer that their payment method is active again.

customer_payment_method_failed

• When it occurs: The issuing bank has informed the network that the card is no longer valid.

• What it means: The card has expired, been closed, or is otherwise unusable for payments.

💡  Action required? Yes.

• Notify the customer that their payment method needs to be updated

• Prompt them to add a new payment method

• Update any active subscriptions to use a valid payment method

EMV Token Events

You can find the EMV token events in the Frisbii Admin in Customers → Payment methods events.

Network tokens can exist in three states: