The merchant back office for payments

Every payment. One screen.

Money in, money out, refunds, disputes, balances and reports, all on the board below. Nothing here needs a second system to answer it.

Before launch  ·  onboarding first merchants

One payment

Six questions. One screen. No order to follow.

A payment is a thing several people ask different questions about on the same afternoon. The board answers all of them in the same place, so nobody has to know which system holds which answer.

pay_8f21c04b EUR 240.00  ·  14:02  ·  Marta L.

Where did it come from

A hosted checkout page, opened from an email.

Did it clear

Cleared at 14:02 and captured the same second.

What did it cost us

0.98 in fees, on the rate this merchant is on.

Has any of it gone back

60.00 refunded at 16:31, signed off by a named person.

Is anybody contesting it

No dispute open. If one opens, the clock starts here.

When does the money arrive

Tomorrow, inside the payout of 4,712.40 on the board.

Three people asked three of those questions today, and nobody opened a second system.

Two lenses

The same payment, seen twice.

You can put your own name on this and hand every merchant an account. What a merchant is shown is a smaller version of what you are shown, and the difference is decided by the signed session rather than by the screen.

What you see

Amount240.00
Merchant fee0.98
Our cost0.41
Margin0.57
Route takenrail B
Settlestomorrow

What your merchant sees

Amount240.00
Fee0.98
Settlestomorrow

The three rows a merchant never sees are removed by one layer, in one place, so a screen built next month inherits the rule by existing.

The legend

Everything the board can show.

Every line here is built and walkable in the product today, unless the line says otherwise.

Taking money

Payment linkslive
A hosted checkout pagelive
Instant bank railslive
Cards and bank transferslive
Six currencieslive
Your own checkout, over the APIlive

Moving money out

Withdrawals with an approval queuelive
Payout batcheslive
Saved beneficiarieslive
Payout scheduleslive
Early settlement requestslive
A named approver on every releaselive

Keeping it straight

Refunds with approvalslive
Disputes with a full lifecyclelive
Balances and a full ledgerlive
Settlement scheduleslive
Reports, exports and insightslive
Keys, webhooks and a sandboxlive

The board is opened area by area on the product pages, and the keys and webhooks behind it sit with the developers.

At the desk

Four people, one board.

Support answers a customer about one payment without leaving the screen they are already on.

Finance reads what settles on Friday off the same board support is reading.

The founder looks once and sees the whole day, with no report to request.

Your merchants get their own account, showing their own half of it.

Each of these has its own page on who it is for.

Open the board with us for half an hour.

We follow one real payment from the checkout page through to the money arriving, and answer whatever comes up on the way.

hello@orchespay.com