Payment method mapping errors

If orders are landing in Order Exceptions because of a payment method, here’s what to check.

Confirm you’re mapping the exact payment method

TruSync matches on the exact payment method name your store reports — a mapping for “Credit Card” won’t cover an order that came through as “Visa” if your store reports them separately. Open the exception to see the exact payment method name TruSync received, then map that specific name in Settings → Payments.

Marketplace stores don’t need payment method mapping

Amazon and eBay orders post as Invoices, which don’t carry a payment method — if you’re seeing a payment-method exception on one of these stores, something unexpected is happening; contact support from your dashboard.

TruSync won’t auto-map to a default

This is deliberate — an incorrect auto-mapping creates more work later than waiting for an explicit one. Every payment method your store uses needs its own mapping before orders using it will sync.

FAQ

I mapped the payment method — why are older orders still stuck? Existing exceptions clear once the mapping exists; if they haven’t after a short wait, contact support from your dashboard.

Can two different payment methods map to the same QuickBooks payment method? Yes, if that’s how you want them grouped.

What if my store adds a new payment method later? Orders using it will become exceptions until you add a mapping for it, the same as any other unmapped payment method.