Payment orchestration
Payment infrastructure that settles into your own accounts.
Temble sits between your store and your payment providers. Every order is routed across the payment accounts you already own, on rules you write — and the money lands there, never in a Temble account.
- No custody
- Funds settle in your own accounts
- Any channel
- Shopify, WooCommerce or custom
- Your domain
- Checkout served from your subdomain
- On decline
- Automatic retry on your primary
YOUR STORE
Shopify · WooCommerce · Custom
TEMBLE
Routing rules · automatic retry
YOUR ACCOUNTS
Settles where the payment was taken
Works with your platform · payment methods served by your own provider
Why orchestration
A single processor is a single point of failure.
Orchestration is the layer that removes it. Same checkout, same store — but the order can be sent wherever it has the best chance of being paid.
Without orchestration
- One processor takes every order, or none of them.
- A decline is a lost sale — there is nowhere else to send it.
- No way to split volume, cap an account, or keep a funnel on its own setup.
- Every channel reconciles in its own place.
With Temble
- Every account you own is a destination Temble can route to.
- A declined route retries on your primary before the customer notices.
- Split by percentage, cap daily volume per account, pin a funnel to a setup.
- Shopify, WooCommerce and custom orders land in one ledger.
Routing engine
Rules you write, applied to every order.
Temble decides where each payment goes before it reaches a provider — and gets a second chance when the first answer is no.
How it works
Live in three steps.
No replatforming and no code in your theme. Temble takes over at the payment step and hands the order back to your store.
- 01
Connect your store
Install the Shopify app or the WooCommerce plugin, or point a custom storefront at the checkout API. Your theme does not change.
- 02
Connect your payment accounts
Each account you own becomes a destination Temble can route to. Onboarding runs inside Temble, in the form your country of registration actually requires.
- 03
Write your rules
Split by percentage, cap daily volume per account, pin a funnel to one setup. A declined route falls back to your primary.
Unified data
Every channel, one ledger.
Orders paid through different accounts and different storefronts still reconcile in one place — with the account that took each payment written on the row.
- Attribution
- Every payment carries the channel it came from and the account that took it.
- Fees
- The processor fee and the Temble fee are shown per transaction, not estimated.
- One place
- Transactions, customers, payouts and disputes for every channel at once.
| Order | Channel | Account | Amount | Status |
|---|---|---|---|---|
| #4381 | Shopify | Account 01 | €128.00 | settled |
| #4380 | WooCommerce | Account 02 | €64.50 | retried |
| #4379 | Custom | Account 01 | €240.00 | settled |
| #4378 | Shopify | Account 03 | €96.00 | refunded |
Integration
One call stands between an order and a payment.
Two plugins for the platforms most merchants are on, and a signed endpoint for everything else. No SDK to adopt, no checkout to rebuild.
- Shopify
- Install the app; checkout hands off to Temble at the payment step.
- WooCommerce
- Install the plugin, connect in one click, no theme changes.
- Anything else
- One signed POST per order, and a redirect to the URL it returns.
curl https://temble.io/api/gateway/session \
-H "X-Temble-Key: tpk_live_…" \
-H "X-Temble-Signature: ${hmac_sha256(body, secret)}" \
-d '{
"amount_cents": 12800,
"currency": "eur",
"order_id": "4381",
"ref": "shop-4381",
"return_url": "https://yourstore.com/thanks"
}'{
"session_id": "b1f0…",
"pay_url": "https://pay.yourstore.com/s/b1f0…"
}Reach
Where your business is registered decides what it is asked for.
Onboarding reads the requirements of your own country of registration — the trade licence in the Emirates, the SIREN in France, the EIN in the United States — and asks for those, not a form written for somewhere else.
- 110
- Countries a business can onboard from
- 46
- With local card acquiring
- 64
- Served by cross-border payouts
Coverage follows your payment provider. Settlement happens in the account you connected, in its own currency.
Trust
Where your money actually goes.
Three properties of how Temble is built. Each one is verifiable from your own provider dashboard.
No custody
Your money never sits with Temble
Payments are processed by the accounts you connected and settle directly into them. Temble's fee is collected as a platform fee on the transaction — your revenue never passes through a Temble bank account.
No card data
Card details never reach our servers
The payment fields are served by your provider on the hosted checkout page. Temble sees the amount, the order and the result — never a card number.
Your domain
The checkout stays on your brand
The hosted page runs on your own subdomain with your published design, so a customer never lands somewhere they do not recognise to pay.
FAQ
Payment orchestration, explained.
How Temble routes payments, what the dashboard shows, and where your money actually goes.
- 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. If a routed setup refuses a charge, Temble automatically falls back to your primary setup so the sale isn't lost.
- Which platforms does Temble connect to?
- Temble integrates with Shopify and WooCommerce through native plugins, 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 at a glance, plus a full transaction list with the sales channel (Shopify, WooCommerce or custom) attributed to every payment.
More questions? See supported integrations, review pricing or book a demo.
Build your payment stack on accounts you own.
Connect your store, connect your payment accounts, write the rules. Temble handles the rest of the way to the money — which never stops being yours.