Map a payment gateway

An order carries the gateway it was paid through, named the way the store names it. Mapping tells Yessort which payment method that gateway means.

On the channel's settings under Integrations. Needs organisation-admin access.

Gateways find you

You do not have to predict the names in advance. The first time Yessort sees an unfamiliar gateway on an order, it records it as seen but unmapped and shows it to you.

So the usual sequence is: orders arrive, an unmapped gateway appears, you map it. Nothing needs configuring before you go live.

Steps

1. Open the channel's payment settings.
2. Find the gateways listed as unmapped.
3. Against each, choose the Yessort payment method it corresponds to.
4. Save.

Mapping catches up on what came before

Mapping a gateway also applies to the transactions that were waiting on it. Orders that arrived while it was unmapped are picked up — nothing is lost by mapping it late, and there is no need to rework those orders by hand.

The fallback

A channel can have a default payment method, used for an order whose gateway matches nothing you have mapped. It keeps orders moving while a new gateway is waiting to be mapped.

Without one, a payment on an unrecognised gateway waits until you map it.

Naming

Map to the payment method that reflects how the money actually reaches you, not just the gateway's label. Where two stores both report the same gateway name but settle into different accounts, they need separate payment methods — mappings are per channel, so each store maps its own.

What happens after mapping

Yessort records which payment method an order was paid by. What is then posted to your accounting system is covered in Accounting.