White-label payment operations

Payments, routing and payouts.
One console.

Connect banks and MIDs, route every payment by rule, fall back when a bank says no, ship a branded checkout — and keep balances, FX and payouts next to the transactions that made them.

Request a demo See it move
Dashboard 1D7D1M Live

Transactions

0

Success rate

0

Transactions / sec

0

Volume never summed across currencies

EUR0
UAH0
KZT0

Live transactions 0 / min

    Routing · PRJT_SHOP_EU

    Cascaded → MID_BETA_EURALPHA declined 05 · approved in 412 ms
    2FA
    Payout batch approved240 rows · 3 currencies
    RoutingCascadingWidget studioMulti-currency balancesFX rulesBatch payoutsRefunds & stornoChargebacksRolling reserveApple PayGoogle PayRoles & 2FAAudit logAutomatic reports

    Built for

    Teams that run payments for other people.

    PSPs & payment operators

    Several banks, many merchants, one place to decide which MID takes which payment.

    Fintechs

    Your own branded console and checkout without building the payment back-office first.

    Larger merchants

    A self-service portal: projects, reports, balances and payouts — nothing you didn’t grant.

    01 Routing & cascading

    A rule picks the bank. A decline walks to the next.

    Conditions on type, currency, amount and method send each payment to a MID. When that MID declines, cascading tries the next one in order — and every hop stays on the transaction.

    • Versioned routing: view, edit, history, deploy
    • Explicit fail exit, no silent drops
    • Hop counters right on the graph
    0approved
    0saved by cascade
    Routing / PRJT_SHOP_EUViewv35 Active
    ▶ Start ◇ CONDITION · 3 exits 01 type = payment currency = EUR 02 type = payout 03 Else MID_ALPHA_EUR0 MID_BETA_EUR0 MID_PAYOUT_EUR0 ✕ Fail cascade

    Routing trace PAY_—

      02 Widget studio

      Every pixel of the checkout, set in the console.

      Layout and card form, colours and liquid glass, shape and density, 73 Google Fonts, locales, methods with customer fees and the loader your customers wait on — every change lands in the live preview. A finished widget is cloned per merchant, not rebuilt.

      Watch the tour, or take the controls — they’re real.

      Widgets / Shop EU checkout Live preview

      Pay with

      Card number4242 4242 4242 4242
      Expiry12 / 28
      CVC•••
      CardholderAnna Kovalenko
      NetworkUSDT · TRC20Send to addressTQ7k…p9Xe

      Secured · 3-D Secure

      ✓Payment approved

      03 Analytics

      A board, not a fixed report.

      Transactions, throughput, success rate, errors, declines, volume and refunds. Scope it to the whole system, one merchant, one MID or one bank — down to 15-minute buckets. Volume stays split by currency, never summed across them.

      • Per-widget metric, split and chart type
      • Compared with the previous period
      • Scope by merchant, project, MID or bank
      Analytics
      SCOPEWhole systemBuckets: hourly

      Transactions

      0+0%

      Success rate

      0+0%

      Errors

      00%

      Declined

      00%

      Payment vs payout payment payout

      04 Reports & transparency

      Every payment, with the conversation around it.

      Open a row and read what actually happened: the request, the routing decision, each bank response, the cascade and the callback your merchant received. Heavy extracts go to downloads, or run themselves on a schedule.

      • Transactions, orders, downloads, automatic reports
      • Request & callback logs, routing and cascade trace
      • Export exactly the set you filtered
      TransactionsOrdersReport downloadsAutomatic reports
      TransactionMethodAmountStatus
      Automatic report Daily settlement sent · 09:00

      05 Refunds, storno & chargebacks

      Money goes back the way it came — on the record.

      Full or partial refunds straight from the transaction, only where the MID supports them and the user holds the right. Storno reverses a booking on the balance with a reason, inside a 90-day window. Chargebacks get their own queue.

      • Partial refunds with “already refunded” tracking
      • Per project: refunds by API, by merchant, or both
      • Storno debit / credit with a reason in the audit log
      Transaction PAY_7QK2M9XLAapproved
      Amount€129.00
      Visa •••• 4242MID_ALPHA_EURrefund supported

      Already refunded €0.00Available €129.00

      Who can refund
      roles with manual refund right
      Storno window
      90 days
      Chargebacks
      own queue, per project
      Refund by API Refund by merchant

      Activity ledger · EUR

        Refund

        Amount, EUR

        06 Merchants & projects

        A project holds every commercial term.

        The merchant is the company. The project is the setup: assigned MIDs, fees, rolling reserve, exchange rules, API keys, IP whitelist, callback builder, cascading and routing — on one card, next to its balances.

        • One onboarding model for every merchant
        • Banks and MIDs with their own credentials and fees
        • Callback builder instead of custom code
        Shop EU / PRJT_SHOP_EUActive

        07 Balances, payouts & FX

        The money lives next to the payments.

        Balances per project and currency with settlement, rolling reserve and overdraft. Top-ups, withdrawals, transfers, manual and batch payouts, chargebacks — and FX from your own rate sources and groups.

        Balance · 3 currencies

        EUR652 899
        Rolling reserve
        74 781
        Overdraft left
        10 000 000
        UAH210 400
        Overdraft limit
        400 000
        Overdraft left
        400 000
        KZT1 000 000
        Settlement
        1 000 000

        Exchange rule Group: VIP

        EUR1 000.00
        UAH0.00

        rate 45.2130source: ECB · markup 0.8%

        Batch payout payouts_oct.csv

        0processed
        0paid
        0failed
        240rows

          Operations

          • ↓Top-up+€25 000
          • ↑Withdrawal−€8 200
          • ⇄Transfer EUR → UAH€3 000
          • !Chargeback CB-2291−€129.00
          • ◷Overdraft used12%

          08 Two portals, your brand

          One product. An operator console and a merchant portal.

          Operators see everything. Merchants see their projects, reports, balances and payouts — nothing else on the menu. Logo, colours, checkout theme and docs and support links are yours.

          admin.yourbrand.com

          All merchants · 14 projects

          Today volume€1.92M
          Success rate99.4%
          Active MIDs23

          09 Security & control

          Built for people who get audited.

          Two-factor sign-in

          On both portals, for every user.

          Roles, view vs manage

          Permission groups with separate rights.

          ViewManage
          Payouts
          Routing
          Card PANs

          Audit log

          Who changed a fee, a rule, a user or a payout — with before and after.

            Wallet identities

            Certificates, Apple Pay and Google Pay merchant IDs.

            • Apple Paymerchant.com.yourbrandvalid · 284 d
            • Google PayBCR2DN4T…verified

            Cards behind a permission

            Customers, cards and PANs, each with its own right.

            4242 •••• •••• 4242masked · no PAN permission

            How it works

            From first bank to first payout.

            1. 1

              Connect providers

              Add banks and their MIDs with credentials, fees and required fields.

            2. 2

              Set up projects & routing

              Assign MIDs, fees, reserve and FX; draw the routing and the cascade.

            3. 3

              Take payments, pay out

              Launch the branded checkout, watch the board, run payouts from balances.

            Demo

            Ready to run your own payment console?

            We’ll walk the admin and the merchant portal on your flow: the board, a routing rule with a cascade, a project setup, and a payout run.

            • Analytics on a question you actually ask
            • Routing, cascade and the trace left on a payment
            • How a merchant is onboarded onto the portal