Duplicate Stripe customer match conflict
This article explains what to do when the Stripe Customer adoption wizard finds a conflict — either a Stripe customer that matches multiple members, or a member that matches multiple Stripe customers.
What’s happening
Section titled “What’s happening”The auto-match compares your existing Stripe customers against your member records by email and name. When a one-to-one match can’t be determined, a conflict row appears:
- One member, multiple Stripe customers — two or more Stripe customer records point to the same member (for example, the member used different email addresses over time or had duplicate records in your prior system).
- One Stripe customer, multiple members — two members share the same email or name and the system can’t decide which one the Stripe customer belongs to.
How to fix it
Section titled “How to fix it”- In the Stripe customer adoption wizard, find the conflict rows. They’re flagged with a conflict indicator in the match list.
- For each conflict row:
- If one member matches multiple Stripe customers: review the customers listed and select the correct one using the radio control on the row. The correct customer is usually the one with the most recent payment history. Leave the others unmatched.
- If one Stripe customer matches multiple members: use the dropdown on the row to select the correct member. If the customer belongs to neither, leave the row unmatched.
- Select Apply matches to commit your selections.
If you’re unsure which Stripe customer to keep, open your Stripe Dashboard and compare transaction histories by customer ID.
If that didn’t work
Section titled “If that didn’t work”If the conflict row shows an error after you’ve selected a match and applied it:
- Try the Re-match option on that row to re-run the auto-match for it specifically.
- If the error persists, use the Upload a CSV instead option to provide a manual mapping of Stripe customer IDs to member IDs. The CSV path bypasses the auto-match engine.
- If you’re still blocked after the CSV path, contact MapleGather support with the Stripe customer ID and the member ID from the conflict row.
Stripe customer records left unmatched are not linked to any member. Those members must re-enter their card at their next checkout. You can re-run the adoption wizard at any time to match customers you left unmatched on the first pass.