Seamless Payment Gateway Migration: Reconnecting BigCommerce Customers to Saved Cards with Authorize.net CIM

Navigating Payment Gateway Migrations: Reconnecting BigCommerce Customers to Saved Cards (Braintree to Authorize.net)

In the dynamic world of e-commerce, businesses often find themselves needing to migrate payment processors. Whether driven by cost, features, or strategic partnerships, this transition is a significant undertaking. One of the most critical, yet frequently overlooked, aspects is ensuring the seamless transfer and re-linking of saved customer payment information. Failing to do so can lead to a frustrating customer experience and potential cart abandonment.

A recent discussion in the BigCommerce forum perfectly illustrates this challenge. A merchant, Andrew Lustig, initiated a thread detailing his journey from Braintree to Authorize.net. He successfully exported customer data, including saved credit card information, from Braintree and imported it into Authorize.net. Authorize.net, in turn, provided a mapping of old Braintree customer codes to new Authorize.net customer codes. The core question, and a crucial one for maintaining customer trust and convenience, was how to update BigCommerce customer records with these new Authorize.net reference numbers so that previously saved payment information would be accessible at checkout.

The Migration Conundrum: Bridging Braintree, Authorize.net, and BigCommerce

Andrew's scenario is common: a merchant has taken the essential first steps of migrating sensitive payment data directly between payment gateways. The data now resides securely within Authorize.net. The challenge lies in informing BigCommerce how to access and display this migrated data for the correct customer. BigCommerce doesn't store sensitive card data itself; instead, it relies on a secure tokenization service provided by the payment gateway, typically linking a BigCommerce customer ID to a corresponding customer profile within the gateway's system.

Essential Steps for Authorize.net Integration with BigCommerce

Daniel Olvera from Trepoly.com provided an excellent starting point, outlining the non-negotiable steps for integrating Authorize.net with BigCommerce, especially when dealing with migrated saved cards:

• Enable Customer Information Manager (CIM) in Authorize.net: This is paramount. Authorize.net's CIM service is their tokenization and customer profile management system. It must be specifically enabled within your Authorize.net Dashboard. BigCommerce relies heavily on CIM to communicate with Authorize.net, securely store customer payment profiles, and retrieve saved cards for returning customers. Without CIM, BigCommerce cannot access or manage saved cards on the Authorize.net platform.
• Verify Data Mapping: After the data transfer from Braintree to Authorize.net, Authorize.net typically provides a mapping file. This file links your original Braintree customer identifiers to the new Customer Profile IDs and Payment Profile IDs created within Authorize.net. Thoroughly verifying this mapping is critical. It's the key to understanding how your BigCommerce customer records should ideally link to the new Authorize.net profiles.
• Enable Settings in BigCommerce: Within your BigCommerce dashboard, you must activate the stored card functionality for Authorize.net. Navigate to Settings > Payments, click the Authorize.net tab, and check the box for "Enable stored credit cards/debit cards". Save your changes. This tells BigCommerce to communicate with Authorize.net's CIM service to present saved card options at checkout.

These steps lay the groundwork, but as Andrew's follow-up question revealed, they don't fully address the core issue of re-linking pre-existing, migrated saved cards.

Illustration: Enabling stored credit cards in BigCommerce's Authorize.net payment settings.

The Missing Piece: Reconnecting BigCommerce Customer Records to Migrated Profiles

Andrew's critical question, "How do I update the BigCommerce customer record to the new payment profile id?" highlights a common challenge. While BigCommerce provides robust API access for customer data, its native payment gateway integrations typically create and manage the links to gateway customer profiles (like Authorize.net CIM Profile IDs) when a customer first saves a card through the BigCommerce checkout. There isn't a direct, standard field on the BigCommerce customer object that you can simply update with a pre-existing Authorize.net CIM Profile ID to magically re-link migrated cards for the native checkout experience.

This is where the complexity truly arises. Here are the primary approaches and considerations for bridging this gap:

1. Gateway-Side Matching (The Ideal Scenario)

The most seamless solution relies on Authorize.net's migration process being sophisticated enough to link the imported payment profiles to its own customer profiles using a common identifier that BigCommerce already sends during a transaction. This common identifier is typically the customer's email address or, less commonly, the BigCommerce customer ID if it was part of the original Braintree export and subsequently imported into Authorize.net.

If Authorize.net's CIM system can match its migrated profiles based on the email address provided by BigCommerce during a checkout attempt, then when BigCommerce requests saved cards for a specific customer, Authorize.net should return the correctly linked, migrated profiles. This requires thorough communication with Authorize.net's migration team to understand their matching capabilities.

2. Custom Development and API Integration (For Advanced Control)

If gateway-side matching isn't sufficient, a custom solution might be necessary. This is a more complex undertaking, often requiring a BigCommerce development partner like Big Migration:

• Storing Authorize.net CIM Profile IDs: You could potentially use the BigCommerce Customers API to store the Authorize.net Customer Profile ID in a custom field on each BigCommerce customer record.
• Custom Payment App/Middleware: However, simply storing this ID won't automatically make the native BigCommerce checkout use it. A custom BigCommerce app or middleware solution would be required. This app would intercept payment requests, read the stored Authorize.net CIM Profile ID from the BigCommerce customer's custom field, and then make direct API calls to Authorize.net to retrieve and present the saved cards to the customer, or to process transactions using those cards. This bypasses or augments BigCommerce's native integration and represents a significant development effort.

// Example (conceptual) of updating a BigCommerce customer with a custom field
// This custom field would then need to be read by a custom payment integration.
{
  "email": "customer@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "custom_fields": [
    {
      "name": "Authorize.net CIM ID",
      "value": "CIM_PROFILE_12345"
    }
  ]
}

3. Customer Re-entry (The Last Resort)

In scenarios where the technical complexity or data volume makes a custom integration impractical, the most straightforward, albeit least ideal, solution is to have customers re-enter and re-save their payment information with Authorize.net through the BigCommerce checkout. This process will automatically create new, correctly linked CIM profiles for each customer within Authorize.net, managed by BigCommerce's native integration. While it impacts customer convenience, it guarantees a clean and functional setup.

Featured Illustration: A seamless flow of payment data during a BigCommerce migration between Braintree and Authorize.net.

Best Practices for a Smooth Payment Gateway Migration

Regardless of your chosen approach, a successful payment gateway migration hinges on meticulous planning and execution:

• Early Communication: Engage with both your old (Braintree) and new (Authorize.net) payment processors well in advance. Understand their data export/import capabilities and any specific requirements for token migration.
• Detailed Data Mapping: Thoroughly review any mapping files provided by your new gateway. Ensure you understand how old customer identifiers translate to new ones.
• Comprehensive Testing: Utilize sandbox environments for both BigCommerce and Authorize.net to conduct extensive testing. Test every payment scenario, including new card saves, using saved cards, refunds, and failed transactions.
• Clear Customer Communication: Inform your customers about the migration. If re-entering cards is necessary, explain why and guide them through the process. Transparency builds trust.
• Consider a Phased Rollout: For high-volume stores, a phased rollout or a period of running both gateways concurrently (if feasible) can minimize disruption.

Conclusion: Expertise Makes the Difference

Migrating payment gateways on BigCommerce, especially when dealing with saved customer payment information, is a nuanced process. While the initial data transfer to the new gateway is a critical step, ensuring BigCommerce can effectively leverage that migrated data requires a deep understanding of both platforms and their respective APIs. Simply enabling CIM and checking a box in BigCommerce isn't always enough to re-link pre-existing profiles.

For merchants navigating these complex integrations, partnering with an experienced e-commerce migration expert is invaluable. At Big Migration, we specialize in guiding BigCommerce stores through seamless transitions, ensuring your development and integrations are robust and your customer experience remains uninterrupted. Don't let payment migration hurdles impact your business – contact us today for expert assistance.