Stripe

TabaPay supports existing Stripe customers in two ways: through migrating stored card data from Stripe to TabaPay, or processing new transactions through TabaPay while continuing to use Stripe's Vault and Forward API.

Who is this for?

✅ Do you process with Stripe today? (i.e. are you an existing Stripe customer?)

👍 If the answer is Yes, use Stripe's Vault and Forward API to process with TabaPay and add TabaPay to your processing stack. Also find information on how to store cards and process with TabaPay.

Vaulting + Storing Cards at TabaPay

The section here will provide details of different cases.

Existing Cards at Stripe

View Detils for Migrating Existing Cards at Stripe

The following diagram shows how to support all existing customers by sharing a bulk file of all PANs from Stripe to TabaPay.

At a high-level, migration of existing card data from Stripe to TabaPay involves four steps:

  1. Initiate migration with Stripe
  2. Secure transfer of migratable data from Stripe to TabaPay
  3. TabaPay Token Generation
  4. Receive all tokens and subscribe to TabaPay Account Updater (Recommended).

Working Details of the Migration

Follow the steps below in more detail.

1. Initiate Migration with Stripe

Provide Stripe with TabaPay’s contact email: [email protected] to initiate the migration process. Stripe will commence work with the TabaPay team to securely transfer your credit card data.

TabaPay meets Stripe’s requirement as an additional processor for you.

  • This includes meeting the processor’s current PCI Attestation of Compliance (AOC), or their listing on Visa’s Global Registry of Service Providers.

Note: TabaPay is a registered processor within Visa’s Global Registry of Service Providers

The processor’s Pretty Good Privacy (PGP) public encryption key, which must be 4096 bits or greater in length. This key must be hosted over HTTPS on one of the processor’s domain names referenced in their AOC or Visa Registry listing.

Note: The TabaPay PGP public encryption key is 4096 bits or greater in length, and is hosted over HTTPS on one of TabaPay's domain names referenced in the AOC.

2. Secure transfer of migrate-able data from Stripe to TabaPay

Stripe prepares an encrypted JSON export file containing your data, including the card details of your customers, email addresses, and any attached metadata. We then arrange a secure transfer with TabaPay, who uses this file to import the data into their system.

For every unique PAN on their file, Stripe provides to TabaPay:

  • Stripe Processor ID
  • Stripe token
  • Client ID at Stripe
  • PAN
  • Exp Date (as available)
  • Name on Card (as available)
  • Billing Address (as available)
  • Metadata (Conditional)
{
    "customers": \[
        {
            "id": "cus_abc123def456",
            "email": "[[email protected]](mailto:[email protected])",
            "description": "Jenny Rosen",
            "default_source": "card_edf214abc789",
            "metadata": {
                "color_preference": "turquoise", ...
            },
            "cards": [
                {
                    "id": "card_edf214abc789",
                    "number": "4242424242424242",
                    "name": "Jenny Rosen",
                    "exp_month": 1,
                    "exp_year": 2020,
                    "address_line1": "123 Main St.",
                    "address_line2": null,
                    "address_city": "Springfield",
                    "address_state": "MA",
                    "address_zip": "01101",
                    "address_country": "US"
                }, ...
            ]
        }, ...
    ]
}

3. TabaPay Token Generation

For every unique PAN, Client provides to TabaPay:

  • ClientID
  • Old Processor ID, TabaPay ID
  • Name on Card (Optionally)
  • Billing Address (Optionally)
  • TabaPay merges the two files - from Stripe and Client (with guidance from Client on what to choose for Billing Address and/or Name on Card) and creates the following:
    • Client ID
    • TabaPay Token (Account ID)
    • Name on Card
    • Billing Address
Optional: Enhanced Data

During migration TabaPay can run Query Card API on every PAN and return additional data.

  • Client ID
  • TabaPay Token (Account ID)Name on Card
  • Billing Address
  • Network Response Code
  • AVS Response Code
  • CVV2 Response Code
  • ANI Response Code
  • BIN
  • Last 4
  • Issuer Name
  • Pull:
    • Enabled or not
    • Card Network
    • Card Type
    • Regulated or Exempt
    • Issuer currency
    • Issuer country
  • Push:
    • Enabled or not
    • Card Network
    • Card Type
    • Regulated or Exempt
    • Issuer currency
      • Issuer country
    • Fast Funds Availability

4. Receive Tokens and subscribe to TAU

TabaPay Tokens provide the authorization improvements that network tokens offer for lifecycle management events through TabaPay Account Updater (TAU). Contact TabaPay or email [email protected] to enable TAU. TAU billing applies only to updated credentials.

Once TabaPay Tokens are issued, you will be able to process card payments using Create Transaction API.

Processing Transactions with TabaPay

New Card Add using TabaPay

TabaPay offers a fully customizable, PCI-compliant UI widget to collect the external debit card details. Your customer may need to provide their external debit card postal code to complete AVS verification. TabaPay has several tools for all your pre-processing needs.

👍

TabaPay Dynamic iFrame for PCI-compliant Add Card

Install TabaPay's Dynamic iFrame to enable you add new cards from your customers. Upon adding cards, the iFrame returns a TabaPay token that can be then used during processing.

  1. You install the Basic Custom iFrame and accept customer information on the form.
  2. TabaPay returns the Iframe token to you.
  3. You send the Query Card API request to check for push and pull capabilities.
  4. TabaPay returns with the API response.
  5. You send the Create Transaction API using the iframe Token.

Note: You can use the TabaPay Tokens if initiate Create Account API right before sending Create Transaction.

  1. TabaPay returns the API response.

Once in possession of TabaPay Token, TabaPay clients will be able to check eligibility around push and pull using TabaPay's Query Card API. request.

And then continue to process payments, push or pull, using TabaPay's Create Transaction API.

📘

TabaPay Account Updater

TabaPay Clients can keep their cards refreshed and up to date using TabaPay Account Updater.

New Cards Added at Stripe

📘

Stripe Vault and Forward Reference: https://docs.stripe.com/payments/vault-and-forward

  1. Create PaymentMethod with Stripe.

  2. Outbound Proxy to TabaPay using Create Account API to generate an accountID.

  3. TabaPay Token is returned to Stripe.

  4. Stripe sends the TabaPay Token to you.

  5. You send Query Card API to check for push and pull eligibility.

  6. TabaPay returns the API seponse.

  7. You send Create Transaction API to TabaPay with a TabaPay Token.

  8. TabaPay sends the API response

If using Stripe's SDK to vault and forward, TabaPay Clients must know that they will be able to receive a TabaPay Token as a paymentmethod from Stripe.

Once in possession of TabaPay Token, TabaPay clients will be able to check eligibility around push and pull using TabaPay's Query Card API.

And then continue to process payments, push or pull, using TabaPay's Create Transaction API.

TabaPay Sheild

While using multiple processors, you can set up TabaPay Shield features to help fight fraud and reduce risk.

More Resources

Chargeback Reason Codes and Network Mandates

FAQ

1. Will I be able to do card-level controls if I manage multi-processor where one processor is Stripe and the other is TabaPay?

Yes, TabaPay returns relevant values back in Query Card API, and Create Transaction API responses that enables manage card level controls.