Next Payment · payment infrastructure and AI operations

Your next payment, prepared before you ask.

AI prepares the cross-border payment work. Your team reviews the customer price and confirms release. An applicable licensed partner processes the payment.

See the workflow View docs

Payment infrastructure, AI-prepared · see what is live

Through licensed partners · subject to jurisdiction

Read + draft

what an agent gets through the API, the MCP endpoint or the console — never release

corridor with a customer price today; everything else is described by readiness, not by a rate

Q4 2026

launch target — join the early-access waitlist

Live

open · public base URL and join the waitlist

Payment infrastructure

Collect, pay on behalf and pay out — with the partner layer named.

Four product jobs sit under the AI layer. Money movement runs through applicable licensed partners, subject to jurisdiction.

Collect 01

Eligible virtual-account and account-detail arrangements, so a customer, invoice or entity can be matched to its own collection reference. The account layer is operated by the applicable licensed partner.

Pay on behalf 02

Approved funding and sender-of-record arrangements for business and individual recipients, only where the funding model, recipient type and partnership permissions allow it.

Payout 03

Local bank and wallet payout endpoints, submitted through the applicable payment infrastructure partner. We name a market, a method and a rail only where our evidence supports all three.

Price and track 04

The customer quote, the approval, the partner status and the reconciliation, on one record. Read and draft are live; movement stays with the partner.

Corridors & routes

One corridor has a customer price today. Other routes are described by readiness, not by a rate, and the applicable partner is confirmed during onboarding.

Availability depends on jurisdiction, partner onboarding, compliance review and beneficiary checks.

The workflow

Describe the flow. Review the draft. Approve the release.

A governed workflow in four steps. A plain-language prompt becomes a versioned, policy-gated definition. A named person reviews and approves before anything runs.

workflow studio launching

PROMPT

“Every Friday, pay approved supplier invoices under HKD 200,000. New beneficiaries get a 24-hour cool-off. Our finance lead approves each batch.”

Plain language in. The system drafts.

AI DRAFT · WORKFLOW DEFINITION v1

workflow: supplier-payout-approval
trigger: schedule.friday
limits: { per_invoice_max: 200000, currency: HKD }
beneficiary_policy: { new_beneficiary: cool_off_24h }
approvals: [ { role: finance_lead, named: true } ]
policy_gates: [ schema, approvals, policy ]
corridors: [ partner_review ]
evidence: sha256_hash_chain

Drafted with AI and ready for named review. Corridor availability is subject to partner review and jurisdiction.

Payment workspace

Join the waitlist

Build on it

The surfaces finance and developers share.

One REST API, one MCP server, signed webhooks and OAuth for partner apps. Capability status is published below and kept honest.

Capability	Status
Payment Core REST API	Live
Signed webhooks	Live
OAuth for partner apps	Live
Next MCP server	Live · read + draft
On-ramp orchestration	Live · settlement through licensed partners, subject to jurisdiction
Off-ramp orchestration	Live · settlement through licensed partners, subject to jurisdiction
Workflow Studio	At launch
Reference App	At launch
Card issuing	Not supported

Regulated money movement is never described as available or guaranteed by us. Where an API drives a partner-dependent outcome, both facts are stated together.

MCP · tools/callworkspace

POST /mcp
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call",
  "params": { "name": "get_balances", "arguments": {} } }

// response
{ "jsonrpc": "2.0", "id": 1, "result": {
    "resultType": "complete",
    "content": [ { "type": "text",
      "text": "{ \"code\": 200, \"msg\": \"success\",
        \"data\": { \"balances\": [ {
          \"currency\": \"SGD\", \"available\": 184250.5,
          \"status\": \"Available\" } ] } }" } ] } }

Example output. Regulated outcomes stay Partner review or Compliance review.

MCP verb list · read + draft

get_accountsread
get_balancesread
get_transactionsread
get_beneficiariesread
get_payout_statusread
get_fx_referenceread
get_compliance_statusread
draft_payoutdraft
prepare_reconciliationdraft

Release, approve, policy write and wallet sign are never exposed through MCP.

Get started

Read the docs to create an account and connect an AI assistant through MCP.

View docs Join the waitlist

Use cases

Built for the way Asia moves money.

Three of the workflows finance and treasury teams run most. Each one turns chat messages and spreadsheets into one governed record.

Pay Asian suppliers

Payout approvals run through chat and spreadsheets today. FX is checked by hand before each batch.

The send flow drafts the payout, screens it and routes it by amount threshold. The FX reference rides on the draft.

send template · Payment Core API · evidence events

Reconcile across entities

Three entities, three sets of statements, nightly manual matching.

Per-entity accounts with segregated records and an exception queue tiered by amount. A finance lead approves exceptions above threshold.

reconciliation workflow · accounts · control plane roles

Embed payouts in your product

Building approval logic and evidence trails in-house takes months of engineering.

Connect through REST and webhooks. Approval and evidence come from the control plane. Empty approval chains are rejected.

REST API · OAuth · signed webhooks

See the workflow View docs

All use cases →

Pricing transparency

One corridor has a customer price today. We show you that one.

We publish a corridor price only when a customer can actually get it. Today that is a single corridor; everything else is described by readiness, not by a rate.

Customer quoteLive

Source amount: SGD 4,200.00
Target currency: THB
Customer rate: shown at quote time
Our fee: shown as one amount
Estimated recipient amount: shown before approval

Your quote is issued when the payment is created, and these are the fields you will see.

What decides your price

The corridor — source currency, destination currency and destination country.
The customer rate and our fee, quoted together as one price for you.
The quote's validity, if it expires. When it does, a fresh price is issued and the payment is reviewed again.

Reference rates in our tools and documentation are not executable. They never lock a price, and they are not what a customer pays.

Card issuing is not part of the product. Next Payment is a technology provider: not a bank, not a custodian, not a card issuer.

Bring one workflow. See it governed.

Bring one payment workflow you run today. We map it to a governed definition and show the approval structure and evidence trail it would produce. Thirty minutes, no commitment, working from your own workflow.

See the workflow View docs

Prefer to talk it through? Talk to sales.