Customer Upload – Bulk Import Process

When to Use Bulk Upload:

• Migrating from another gateway (Authorize.net, Stripe, PayPal, Square)
• Moving from spreadsheet/manual system to gateway
• Importing customer database from accounting software
• Onboarding large customer base at once

Upload Process:

1. Prepare CSV File:
   
   The CSV must be properly formatted with specific column headers.
   
   Mandatory Headers:
   • Identifier or Customer ID: Unique identifier for each customer
     • Example: “CUST001”, “12345”, “ABC-Company”
     • Used to match and prevent duplicates
   • Customer Name or First Name and Last Name
   • Email Address
2. Optional But Recommended Headers:
   • Phone
   • Company
   • Address
   • City
   • State
   • ZIP
   • Country
   • Card Number (for storing payment methods)
   • Expiration (for cards)
   • Routing Number (for ACH)
   • Account Number (for ACH)
3. Critical Date Formatting Issue:
   
   Excel often formats dates incorrectly. When you type “05/26” (May 2026 expiration), Excel converts it to “44563” (Excel’s internal date format).
   
   Fix for Expiration Dates:
   • Open your CSV in Excel
   • Select the entire Expiration column
   • Right-click → Format Cells
   • Select Text format (not Date, not Number)
   • Re-enter expirations as “05/26”, “12/27”, etc.
   • Verify they display as text, not numbers
   • Save the file
4. Navigate to Customer Upload:
   • Go to Customers tab
   • Click Upload or Import Customers button
5. Upload File:
   • Click Choose File or Browse
   • Select your prepared CSV
   • Click Upload
6. Map Fields:
   • System may show field mapping screen
   • Match CSV columns to gateway fields:
     • Your “Client ID” → Gateway “Customer Number”
     • Your “Email” → Gateway “Email Address”
     • Your “CC Number” → Gateway “Card Number”
   • Click Confirm Mapping
7. Processing:
   • System processes each row
   • May take several minutes for large files
   • Progress bar shows status
8. Review Results:
   • System provides upload summary:
     • Total rows processed
     • Successfully imported
     • Failures/errors
   • Download error report if any failures
   • Common errors:
     • Duplicate customer IDs
     • Invalid card numbers
     • Incorrect date formats
     • Missing required fields
9. Fix Errors and Re-Upload:
   • Fix any failed rows in your CSV
   • Re-upload just the failed rows
   • Or re-upload entire file (system handles duplicates)

Data Security During Upload:

• File is encrypted during transmission
• Cards are immediately tokenized upon upload
• Raw card numbers are never stored
• File is deleted from upload server after processing

Migration Tips from Other Gateways:

From Authorize.net:

• Export Customer Information Manager (CIM) data
• Customer IDs map directly
• Payment profiles become wallet entries

From Stripe:

• Export customers and payment methods via Stripe Dashboard
• Customer IDs map to Identifier field
• Payment tokens can be migrated if processors match

From PayPal:

• Export subscriber list
• PayPal Customer IDs become your Identifier
• Stored payments require re-entry (can’t migrate PayPal tokens)