ActTrader · Payment software Live

Run the payment business. We'll be the software behind it.

You already have the clients, the licence and the acquiring relationship. What you don't have is the software to be a payment service provider to your own merchants. That is the part we make.

LiveIn production today
OneClient, ledger and back office
25+ yrsOne codebase since 2000
merchant.yourbrand.com / pay
Hosted checkoutLink · QR · POS
BalancesFiat IBAN · crypto
Card acquiringBy MID · TID
SettlementsBank · wallet
API keys · webhooks · docs

The boundary

We are not a payment company.

ActTrader owns and operates the technology. It is not a payment company, an acquirer, an issuer or a custodian. You bring your own acquiring and your own licence; you onboard your own merchants; their customers pay through your pages, under your brand. We never touch the money and we never appear to your merchants.

What your merchants get

A merchant portal you put your name on.

Every merchant you onboard gets their own portal, branded as yours.

Get paid

Hosted checkout, pay-by-link and QR, a point-of-sale screen, embeddable payment buttons.

Hold and move

Fiat balances with IBAN and statements, crypto wallets with per-network deposit addresses.

Card acquiring

Takings by MID and TID, with acquirers routed by your rules.

Settlements

Card to bank and crypto to wallet, with rolling reserve and a payout account.

Invoicing

One-off and recurring, a saved client book, templates, terms and reminders.

See everything

Every money event with filters and CSV export, and analytics on volume, success rate, methods and acquirers.

Build on it

API keys with HMAC-signed requests, webhooks, payment buttons and docs.

Their team

Roles from owner down to read-only, with an activity log.

What you get

The console you actually run the business from.

Your merchants see their portal. You get the one behind it: onboarding and KYB review, merchant and licence allocation, provider and credential configuration, settlement cycles, fee configuration and your own back-office staff roles.

Onboarding & KYBLicence allocationProvider configSettlement cyclesFee configurationBack-office roles
Try the platform →
console.yourbrand.com / operator
Onboarding & KYBReview · approve
Licence allocationPer merchant
Providers & credentialsConfigure
Settlement cyclesScheduled
Fee configuration · back-office roles · activity log

Pricing control

Price it your way, and know why every rate is what it is.

Pricing resolves down a six-level ladder - a specific merchant's volume tiers, then that merchant's flat rate, then your tiers, then your default, then the platform seed. The first level with rows wins; levels never blend. A rate can be set per vendor as well as per rail, and each merchant can sit on retail or wholesale pricing. Volume tiers move with a merchant's rolling thirty-day volume.

When someone asks why a transaction was priced the way it was, the system answers: a preview tells you which level and which row produced the rate.

Setup fees, monthly account fees and monthly minimums are handled separately from per-transaction pricing, so a one-off setup charge can never be mistaken for the price of the next payment. Alongside it, a cost book records what your vendors and schemes charge you, so you can see your margin rather than infer it.

The regulatory model

Your licences, modelled properly.

A licence here is a real object: a jurisdiction and a regulator, with the capabilities it backs. You set what each licence permits - which countries, which verticals are prohibited, which assets are allowed, what risk appetite applies - and every merchant is allocated to one. One deployment can therefore serve several regulated markets without pretending they are the same market.

Where one operator sponsors another, that is modelled too: capabilities are granted, signed by both parties, and a sub-delegation requires the original licence holder to countersign. The permission chain is explicit, so it can be shown to a regulator rather than reconstructed.

The ledger

Double-entry, in minor units, or it isn't money.

Every balance is a double-entry ledger posting in integer minor units, at each currency's own scale. Nothing is a floating-point number, and every merchant-owned row carries the operator and the licence that own it. This is the least exciting section on this page and the first thing anyone who has been burned by a payments vendor will check.

Where it fits

One more business line, not one more vendor.

Payments runs on the same foundation as the rest of ActTrader - the trading platform, the investment platform, the crypto exchange and funded-trader programmes. One client record, one ledger, one back office. Adding payments does not mean a second onboarding flow, a second reconciliation and a second support number.

Private walkthrough · No obligation · One business day

You own the client. We power the rest.

You bring the acquiring and the licence. We bring the software behind it - a branded merchant portal, the console you run it from, and a double-entry ledger, on the same client record and ledger as the rest of ActTrader.

Live. An operator is running it in production, processing e-commerce transactions for its merchants.