Money moves at AI Agent speed.
Tell your agent to send the money. Prime Fast Pay picks the rail, runs the checks, and settles in seconds.
Don't call the API. Tell an agent to.
Prime Fast Pay ships a native MCP server that exposes every endpoint as a typed tool. Point any MCP-speaking agent framework at it and let the model handle the call — no glue code, no per-SDK adapters to maintain.
Claude Agent SDK
A managed agent loop with MCP access built in — no prompt orchestration to write yourself.
LangChain / LangGraph
Loads Prime Fast Pay tools through langchain-mcp-adapters into a React agent.
Google ADK
An McpToolset drops the tools straight into a Gemini-powered agent on Vertex AI.
CrewAI
Wire payouts into any role-based crew with MCPServerAdapter — no custom tool classes.
# Claude Agent SDK — agent.py options = ClaudeAgentOptions( mcp_servers={ "prime-fast-pay": { "command": "prime-fast-pay-mcp", "env": {"PRIME_FAST_PAY_API_KEY": "sk_live_xxxxxxxx"} } }, allowed_tools=["mcp__prime-fast-pay__*"], system_prompt="You send payouts. Always confirm the recipient, amount, and method before calling create_payout." ) async for message in query( prompt="Pay John Doe (rec_9x8y7z6w5v4u) $250 via RTP for invoice #4421.", options=options ): if message["type"] == "result": print(message["result"]) # → Confirmed: po_4k29dLmz, $250.00 via RTP, # submitted to rec_9x8y7z6w5v4u
Built to replace the batch file, not sit next to it.
Corporate banking portals move money on their own schedule. Prime Fast Pay moves it on yours — with the status, control, and reach a real disbursement program needs.
Seconds, not days
Payouts move in seconds on instant rails — FedNow, RTP, SEPA Instant, Visa Direct — and same-day everywhere else. No T+1 to T+3 wait.
One integration, every rail
Send to any supported rail and currency without opening a new banking relationship for every corridor you enter.
Retries and reroutes on its own
If a rail degrades, Prime Fast Pay falls back automatically, so a temporary outage on one network doesn't leave a payout stuck.
You always know where a payout is
Real-time status, granular reporting, and role-based approvals replace the opaque batch files of a banking portal.
Pick the rail. We handle the rest.
Every rail is reachable through the same request shape. Route by currency, speed, and destination — Prime Fast Pay picks the corridor and falls back automatically if one is unavailable.
One endpoint. Nine rails. Live now.
A single POST /v1/payouts arrives, the routing engine picks the cheapest instant rail for that corridor, and the funds leave. If a rail degrades mid-flight, the packet reroutes instead of stalling.
| Rail | Speed | Coverage |
|---|---|---|
| ACH (Standard & Same-Day) | 1–2 business days | United States |
| RTP | Seconds, 24/7 | United States |
| FedNow | Seconds, 24/7 | United States |
| Push-to-Card | Minutes | US, CA, UK |
| Virtual Card Issuance | Instant | US, CA |
| Digital Check | 1–3 business days | United States |
| International Wire (SWIFT) | Same day | 160+ countries |
| SEPA SCT | Next business day | SEPA zone |
| SEPA Instant | Seconds, 24/7 | SEPA zone |
Three layers, one payout lifecycle.
Every instruction moves through the same disciplined path — validated, screened, reserved against a ledger, routed, and reconciled — regardless of which rail it lands on, and regardless of whether a human or an agent sent it.
Payout orchestration layer
Receives each instruction, validates it, reserves funds against the ledger, selects the best rail, and tracks the payout through to confirmation — behind one uniform interface.
Merchant & agent interface layer
A REST API and SDKs for automated flows, an MCP server for agent frameworks, a dashboard for manual payouts and approvals, and webhooks that keep your systems synced with every status change.
Compliance, risk & reconciliation
Recipient verification, sanctions screening, and velocity limits run before funds are ever reserved. Settlement is reconciled automatically against every rail's reports.
Five steps, in the order they actually happen.
This is the real sequence a payout moves through — nothing here is reordered for a pitch.
Instruction received
A typed request lands from your backend, the dashboard, or an agent calling create_payout over MCP. The same validation runs either way — an agent gets no shortcut past it.
Screening runs first
Recipient verification, sanctions and PEP screening, and velocity limits execute before a single cent is reserved. The payout cannot advance until they clear — that ordering is enforced by the code path, not documented in a runbook.
Funds reserved on the ledger
The amount posts to a double-entry ledger tied to your account. A balance is never just a number in a row — it's the sum of entries you can always trace back.
Rail selected and routed
Funds leave on whichever rail is fastest and cheapest for that currency and destination at that moment. If it degrades mid-flight, the payout reroutes instead of getting stuck.
Confirmed and reconciled
Webhooks fire on every state change, and settlement is reconciled automatically against each rail's own reports — so month end is a report you read, not a spreadsheet you build.
A payout is one request away.
Send an instruction, get a payout object back, and watch it move through status via webhook — no rail-specific formatting to learn.
- 01Free sandbox, no card required. Full API functionality — most engineers send a first test payout in under an hour.
- 02SDKs for iOS, Android, Flutter, and REST. Recipient bank details are tokenized in the SDK, so sensitive data never touches your servers.
- 03Webhooks for every state change. payout.created, payout.processing, payout.completed, payout.failed.
- 04Integration engineering support. Available at no cost to qualified teams during evaluation.
// Create a payout POST /v1/payouts Host: api.primefastpay.com Authorization: Bearer sk_live_xxxxxxxx Idempotency-Key: 3b1e9c2f-6a0b-4f5d { "amount": 250000, "currency": "USD", "recipient_id": "rec_9x8y7z6w", "method": "rtp", "description": "Invoice #4421" } // Response { "id": "po_4k29dLmz", "status": "submitted", "eta": "2026-08-17T14:02:31Z" }
Handled like it needs to survive an audit — because it does.
Prime Fast Pay is built with the controls a payout gateway needs, not the ones a checkout page can get away with.
Segregated merchant funds
Merchant balances sit in accounts structurally separate from Prime Fast Pay's operating funds, reconciled daily.
Screening before every reserve
Sanctions, PEP, and fraud checks run on every instruction before funds are ever reserved — not as an afterthought.
Zero-trust networking
Mutual TLS on every service-to-service call. No compute instance carries a public IP.
Encrypted, key-managed
AES-256-GCM at rest, TLS 1.3 in transit, ledger data protected with HSM-backed keys.
Multi-region by default
Active-passive deployment across primary and disaster-recovery regions, tested with quarterly failover exercises.
Full audit trail
Every payout's lifecycle is preserved as an immutable event, so any transaction can be reconstructed end-to-end.
Scoped agent keys
An sk_test_ key routes to the sandbox and never moves real money. Production keys can be scoped per tool, per amount ceiling.
Human-in-the-loop approvals
Role-based approval thresholds hold an agent-initiated payout for sign-off above whatever limit you set.
Idempotent by contract
Every write takes an idempotency key, so a retrying agent can't double-send a payout.
Built for platforms that pay a lot of people.
If your business sends payouts to a distributed base of recipients rather than accepting payments from them, Prime Fast Pay is built around your problem.
Marketplaces & platforms
Gig & creator economy
Affiliate & ad-tech networks
Insurance carriers
Brokerages & fintechs
Corporate contractor payments
Questions teams ask before they switch.
Eight things we hear on every evaluation call. If yours isn't here, email hello@primefastpay.com.
What is Prime Fast Pay?
Payout infrastructure for AI agents. One REST API that routes across 9 payment rails — ACH, RTP, FedNow, Push-to-Card, Virtual Card, Digital Check, SWIFT wire, SEPA SCT, SEPA Instant — plus a native MCP server so any agent framework can issue payouts as typed tool calls.
How fast is payout settlement?
RTP, FedNow, and SEPA Instant confirm in under 30 seconds at p95, 24/7. Push-to-Card settles in minutes. ACH settles in 1–2 business days. SWIFT wire settles same day. API p95 latency is under 250ms at 5,000 req/s sustained.
Which payment rails are supported?
Nine: ACH (Standard & Same-Day), RTP, FedNow, Push-to-Card, Virtual Card Issuance, Digital Check, International Wire (SWIFT), SEPA SCT, SEPA Instant. Coverage spans the US, Canada, the UK, the SEPA zone, and 160+ countries via SWIFT.
Do you support AI agents?
Yes. A native MCP server exposes every endpoint as a typed tool — works with Claude Agent SDK, LangChain, Google ADK, and CrewAI. Install with cargo install prime-fast-pay-mcp, set your API key, and the agent has create_payout, retrieve_payout, list_payouts, cancel_payout, and recipient tools.
Is there a free sandbox?
Yes. Full API functionality, no card required, most engineers send a first test payout in under an hour. Sandbox keys start with sk_test_ and never move real money. Production keys (sk_live_) follow a short compliance conversation.
How do you handle compliance?
Sanctions, PEP, and velocity screening run on every instruction before funds are reserved — that ordering is enforced by the code path, not documented in a runbook. Merchant funds are segregated and reconciled daily. Every write takes an Idempotency-Key, and every payout lifecycle is preserved as an immutable event.
What countries are supported?
ACH, RTP, FedNow for the United States. Push-to-Card and Virtual Card for US, CA, UK. SEPA SCT and SEPA Instant for the SEPA zone. SWIFT wire for 160+ countries. Nine rails total, all reachable through a single request shape.
How do I get started?
Three steps. Get an API key from the dashboard, create a recipient with bank or card details, POST to /v1/payouts. Sandbox keys issue in minutes. Full reference and code samples are at /docs.html.
Send your first payout today.
Spin up a sandbox in minutes, or talk to our team about your corridors, volume, and rollout. Production access needs a short compliance conversation first.