Split
Two accounts. One rule. No surprise at capture.
CheckoutRuleAccounts
Payment orchestration
Your checkout.Your accounts.
Temble sits between your store and the payment accounts you already run. You write the rules. Shoppers pay on your domain. The money lands with you — never in a Temble account.
- No custody
- Funds settle in accounts you own
- Every channel
- Shopify, WooCommerce, or a custom API
- Your domain
- Checkout served from your subdomain
- Your rules
- Splits, caps, and a funnel pinned to one account
01 — Routing
The route is a decision you write, not a default you inherit.
Percentage splits, a daily cap on an account, or a funnel pinned to one setup. The same rules follow the store that owns the checkout — a second shop in the organisation does not borrow the first shop’s funnel.
02 — Checkout
The page wears your domain.
Point a subdomain at the hosted checkout. Shoppers stay on a host you control, from the card form through the thank-you view. The design published with the funnel is the one they see.
On a decline
The shopper sees that decline.
A card is not sent on to another merchant account. You choose the route before the charge; the result of that route is what the checkout shows.
03 — How it runs
Live without replatforming the store.
Temble takes the payment step and hands the order back. Your theme stays yours.
- 01
Connect the store
Shopify, the WooCommerce plugin, or a custom storefront signed against the checkout API.
- 02
Connect the accounts you own
Each account becomes a destination Temble can route to. Onboarding follows the form your country of registration requires.
- 03
Write the rules
Split by percentage, cap a day’s volume, or pin a funnel to one setup.
Transactions
This week| Shop | Status | Amount |
|---|---|---|
| Shopify | Paid | $142.00 |
| WooCommerce | Paid | $64.50 |
| Custom | Refunded | $28.00 |
| Shopify | Paid | $210.00 |
04 — Ledger
One list for every channel.
Shopify, WooCommerce and custom checkouts land in the same transactions view, with the shop named on the payment. Refunds, exports and the shop filter read that record — not a description someone typed onto the charge.
Walk through the dashboard05 — Custody
We never hold the money.
Payments run through the accounts you connect and settle there. The platform fee is an application fee on the transaction. Card numbers are collected by the processor’s fields, not by Temble servers.
Read the security overview and the privacy policy.
Questions, in plain language.
- What is payment orchestration?
- Payment orchestration is a layer that sits between your store and your payment providers. Instead of hard-wiring checkout to a single processor, Temble routes each payment across your connected payment setups based on rules you control, and gives you one dashboard for transactions, reporting and analytics across all of them.
- Does Temble hold or custody my funds?
- No. Temble never holds, custodies or pools merchant funds. Payments are processed through your connected payment accounts and settle directly into your own account. Temble's fee is collected as a platform application fee on each transaction — your revenue never passes through a Temble bank account.
- How does payment routing work?
- You define routing rules in the dashboard: split traffic across your connected payment setups by percentage, set daily caps per setup, or pin a specific funnel to a specific setup. The route is chosen before the charge.
- Which platforms does Temble connect to?
- Temble integrates with Shopify and WooCommerce, and with custom or headless storefronts through the checkout API. The same routing rules, checkout design and reporting apply across every channel.
- What reporting and analytics do I get?
- The merchant dashboard shows revenue, orders, top countries and payment-method breakdowns, plus a transaction list with the sales channel — Shopify, WooCommerce or custom — on every payment.
See it on your store.
A 30-minute walkthrough of checkout, routing and the ledger. Bring the stack you run today.