Payment method mapping errors

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.

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.

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.

TruSync does pre-select the choices it thinks are right and show them as suggestions, but they aren’t saved until you click Save these mappings in Settings → Payments. If you opened that screen, looked at the suggestions and navigated away, nothing was saved and your orders are still waiting in Order Exceptions.

A mapping has two halves, and only one of them stops orders syncing. If the QuickBooks payment method is missing, orders become exceptions and you find out immediately. If the deposit account is wrong, orders sync perfectly well and post the money to the wrong account — which normally surfaces weeks later, when a bank reconciliation won’t balance.

Card payments — credit and debit cards, and card-backed wallets like Google Pay and Apple Pay — deposit to Undeposited Funds, because your processor pays them out to your bank in a batch covering many orders. PayPal-branded payments — PayPal, PayPal Pay Later, PayPal Credit, Venmo, and cards taken through PayPal checkout — deposit to your PayPal account, because the money lands in your PayPal balance.

The gateway’s name doesn’t decide which is which. Braintree handles both kinds, and names its own QuickBooks payment method “Braintree (PayPal)” even for card charges. If a payment method’s money doesn’t turn up where you expected, check that mapping’s deposit account first.

Neither does the payment method’s own name. “BigCommerce Payments” runs on Stripe for some stores and on PayPal for others under the identical name, and “Credit Cards” or “Apple Pay” describe what the shopper used rather than where the money lands. Where TruSync has synced orders under a payment method, it reads the settlement from the gateway transaction reference on those orders rather than from the name.

If nothing about the mapping changed but the money started landing in the wrong account, the usual cause is a change on your processor’s side — you switched processors, or turned a new one on alongside the old one. Your payment method names stay the same through that, so the mapping keeps pointing at the old processor’s account and nothing announces the change.

Ask Trudy to “audit my payment methods”. She compares each mapping against where your recent orders actually settled and flags any that disagree, including payment methods that have started settling two different ways. Then correct the deposit account in Settings → Payments; new orders follow the new mapping, and documents already posted aren’t changed retroactively.

Add paragraph text. Click “Edit Text” to update the font, size and more. To change and reuse text themes, go to Site Styles.