MoneySuite MoneySuite Developers
Sign in Create account
Sandbox open · No card required

AI-Powered Financial operations, as an API.

Bill a customer, chase the payment, pay a supplier in their own currency, reconcile it and post it to the ledger — from one key, one base URL and one set of headers.

Create a sandbox account Make your first call
The sandbox moves no real money. The providers behind it are their own test environments, so you can raise invoices, take payments and send money abroad with the same payloads you will use in production.
Raise a payment request 
$ curl https://api.sandbox.moneysuite.co.uk/v1/payments/requests \
    -H "apikey: $MSUITE_KEY" \
    -H "Client-Id: $MSUITE_CLIENT_ID" \
    -H "Content-Type: application/json" \
    -d '{
      "customerId": "cus_8Kd2Rt",
      "amount": 1250.00,
      "isoCurrencyCode": "GBP",
      "dueDate": "2026-09-30",
      "reference": "INV-0284"
    }'

{
  "paymentRequestId": "pr_4Nc7Yq",
  "status": "OUTSTANDING",
  "amount": 1250.00,
  "isoCurrencyCode": "GBP",
  "url": "https://pay.moneysuite.co.uk/r/4Nc7Yq"
}
201 Created Branded, sent, and chasing itself from here. Response abridged.
100+
Countries you can collect from and pay into
35+
Currencies, with funding accounts held in them
0.25%
International payments, from
FCA · PSD2
Regulated rails, safeguarded funds
Quickstart

From nothing to money landing, in about ten minutes

Three steps, in this order — each one needs the one before it.

1

Register an application

One application per integration, each with its own key, so revoking one never breaks the rest. Your Client-Id is shown alongside it — both headers go on every call.

2

Connect what the APIs read

Bank accounts, collection rails, your accounting package. What you connect in the portal decides what the APIs can return — a rail that is not configured is never offered to your customer.

3

Call, then listen

Raise a request, then take the outcome on a signed webhook rather than polling. Every call you made is in API logs, exactly as the gateway saw it.

The surface

Five areas, one platform

The customer you bill, the supplier you pay and the bank account you reconcile against are the same records throughout — not four products wearing one login.

Area What it does Where it starts
Accounts Receivable Invoices, payment links, QR codes, subscriptions and direct debits — collected on the rails you choose, chased by credit control without you. /v1/payments/requests
Accounts Payable Bills read by the scanner, approved on a workflow, then settled — to a supplier down the road or a beneficiary overseas. /v1/payments/bills
Cash & Treasury Every bank account in one position, multi-currency accounts, and conversion at a rate quoted before you commit. /v1/payments/world-settle/currency-exchange
Intelligence Categorisation, reconciliation, forecasting, counterparty and fraud risk — from a model trained on your own confirmed decisions. /v1/counterparty-risk/predict
Messaging Email, SMS and WhatsApp delivery for everything the platform sends on your behalf. /v1/messaging
Intelligence

A model of your business, not everyone's

The judgement calls — what this transaction was, whether this payment is safe, what cash looks like in six weeks — answered by a model trained on one organisation's own confirmed examples. Nothing is shared between clients.

predict

Asks the client's trained model.

The normal path. Fast, and it improves as it is used.

suggest

Asks an LLM, optionally against candidate values you supply.

For a cold start, or when the value set is yours and keeps changing.

learn

Confirms a correct answer.

Every time a person accepts or corrects a result. This is what makes predict good. 
        ┌────────── learn ◀── a person confirms it
        ▼
   trained model ──▶ predict ──▶ answer
        │
        └── not confident ──▶ suggest (LLM) ──▶ answer

Inline

Put the transactions, receivables or payments in the request. The platform stores nothing, so you can run what-ifs freely.

Pull

Omit them, and it reads the client's own data from the platform. Same endpoint, same response shape.

counterparty risk payment fraud transaction intelligence auto reconciliation cashflow & liquidity account insights account anomaly detection cash feed

Retraining happens on its own once enough confirmed examples accumulate. Scores and alerts arrive on a webhook or a Kafka topic — you are told, rather than left to go looking.

The portal

Keys, events and every call you made

The portal is the control panel; the APIs do the work. Most of what you set up here changes what the APIs return.

The Applications screen: your Client-Id, the registration form, and every key you hold
One application per integration, one key each — shown once, revocable on its own.
The API logs screen: recent calls with method, path, service, latency and status
Every call your applications made, as the gateway saw it — method, latency and status.
  • Applications & API keys — sandbox keys issued instantly; production keys once your organisation is approved.
  • Webhooks — an endpoint per application, each with its own signing secret.
  • Deliveries — what was sent, what came back, and what is being retried.
  • API logs — request, response and latency for every call, failures filterable on their own.
  • Configuration — bank accounts, collection rails, international payments, accounting package.
  • Support — a way to reach a person when the logs do not explain it.
Contact us

Talk to the people who built it

A fintech company based in London, building end-to-end billing and payment automation for businesses of every size.

Email

hello@moneysuite.co.uk

Integration questions, sandbox access, or a demo of the platform.

Telephone

(+44) 0203 059 7870

Monday to Friday, 9:00 to 17:30. Closed weekends.

Office

MoneySuite Ltd

Level 18, 40 Bank Street, Canary Wharf, London E14 5NR, United Kingdom.

Start in the sandbox

Create an account, register an application, and make your first call against real payloads. No card, no contract, nothing to uninstall.

Create account Sign in