Skip to content

Authorize.net Import Documentation

Menu Location: Customers > Authorize.net Import

Access Level: Administrator and above

Last Updated: 2026-03-01

Overview

Authorize.net Import allows you to import customer payment profiles from Authorize.net payment gateway and match them to existing customers in your system. This tool is essential when migrating from Authorize.net or reconciling payment data.

Primary Functions:

  • Import customer payment profiles from Authorize.net
  • Match payment profiles to existing customer accounts
  • Update customer payment information automatically
  • Migrate payment data between systems
  • Reconcile missing payment profiles
  • Bulk update payment profile IDs

Page Layout

  • Upload CSV Section: Import customer export from Authorize.net
  • Matching Results Table: Shows matches found
  • Action Buttons: Import matched profiles, skip unmatched
  • Summary Stats: Total imported, matched, skipped

Import Process

Steps:

  1. Export customer data from Authorize.net account
  2. Save CSV file to computer
  3. Go to Authorize.net Import page
  4. Click "Choose File" and select CSV
  5. Click "Upload and Match"
  6. System matches based on email or customer ID
  7. Review matching results
  8. Click "Import Matched Profiles"
  9. Payment profile IDs updated in customer records

What Gets Imported:

  • Payment Profile ID from Authorize.net
  • Customer email (for matching)
  • Payment method type
  • Last 4 digits of card (if available)

Matching Logic:

  1. Exact email match (primary)
  2. Customer ID match (if included in export)
  3. Name + ZIP code match (fallback)

Common Use Cases

Use Case 1: Migrate from Authorize.net to Stripe

Goal: Before switching to Stripe, capture all Authorize.net payment profile IDs for record-keeping.

Steps:

  1. Export all customer payment profiles from Authorize.net
  2. Import CSV via this tool
  3. System stores Authorize.net IDs in customer records
  4. Begin Stripe migration with complete historical data

Use Case 2: Reconcile Missing Payment Profiles

Goal: Some customers missing payment profile IDs after system migration.

Steps:

  1. Identify customers with missing payment info
  2. Export those customers from Authorize.net
  3. Import CSV - system matches and updates missing profiles
  4. Verify all customers now have payment information

Use Case 3: Update Payment Profile IDs After Gateway Change

Goal: Gateway changed profile ID format, need to update all customers.

Steps:

  1. Export new format from Authorize.net
  2. Import CSV
  3. System updates all customer payment profile IDs to new format

Use Case 4: Historical Data Backup

Goal: Preserve payment profile IDs before decommissioning Authorize.net.

Steps:

  1. Final export from Authorize.net before shutdown
  2. Import to store IDs permanently in customer records
  3. Reference if ever needed for payment disputes or chargebacks

Use Case 5: Bulk Payment Profile Assignment

Goal: Assign 500 payment profiles to customers in one operation.

Steps:

  1. Format CSV with customer email and Authorize.net profile ID
  2. Import via tool
  3. System automatically matches and assigns all 500 profiles
  4. Much faster than manual entry

CSV Format Requirements

Required Columns:

  • Email Address
  • Payment Profile ID (from Authorize.net)

Optional Columns:

  • Customer ID
  • Payment Method Type
  • Last 4 Digits
  • Expiration Date

Example CSV: 

Email,Payment Profile ID
[email protected],60123456
[email protected],60123457

Troubleshooting

No Matches Found

Check:

  • Email addresses in CSV match exactly (case-insensitive but spelling must match)
  • CSV formatted correctly
  • Customers exist in system
  • No extra spaces in email addresses

Solutions:

  • Clean up CSV - remove extra spaces, verify emails
  • Manually add customer records if missing
  • Use alternate matching criteria

Partial Matches Only

Situation: 200 in CSV, only 150 matched.

Actions:

  1. Review unmatched entries
  2. Check if those customers exist in system
  3. Manually match difficult cases
  4. Create missing customer accounts if needed

Import Overwrites Existing Profiles

Concern: Don't want to lose existing payment data.

Safety:

  • System typically only updates blank payment profile fields
  • Check settings for overwrite behavior
  • Test with small CSV first
  • Backup customer data before large import

Best Practices

  1. Test first - Import small subset (10-20 records) to verify matching works
  2. Clean data - Remove duplicates and fix formatting before import
  3. Backup first - Export customer list before importing payment profiles
  4. Verify after - Spot-check several customers to confirm profiles assigned correctly
  5. Document - Note date and reason for import for future reference

Quick Reference Card

Task Action
Import profiles Upload CSV, click Import
Preview matches Review matching results before importing
Skip unmatched Click Skip or just import matched ones
Re-try failed Fix CSV, upload again
Verify success Check customer payment info updated

FAQs

Will this import credit card numbers?

No, only payment profile IDs. Actual card numbers never leave Authorize.net for PCI compliance.

Can I undo an import?

Depends on system. May need to manually remove profile IDs or restore from backup. Test with small batch first.

What if customer has multiple payment profiles?

CSV typically imports primary profile. Additional profiles may need manual entry.

How often should I import?

One-time during migration or reconciliation. Not a regular ongoing process.

Does import work with other gateways?

This tool specific to Authorize.net. Other gateways may have different import tools.

End of Documentation

For additional help, contact your system administrator or Kiva Logic support.