Capture funds instantly. Settle securely. Paystack is the first custodial escrow protocol built for autonomous agents — so an AI can act at machine speed without breaking things you can’t unbreak.
Most teams arrive here for one of two reasons: the percentage they pay a processor every month, or the agent they are about to hand a credit card. It is the same rail underneath — pick the door.
Replace a percentage-based processor stack with direct ACH at $0.75 flat and a custom integration that leaves your ERP where it is. A $5,000 invoice costs $145 on cards. Here it costs 75¢.
Payment operations →Custodial escrow with a reversible audit window, per-agent spend caps, and an operator kill switch — so an AI can act at machine speed without breaking anything you can’t unbreak.
Read the protocol →Every payment has a cost/trust trade-off. Agents shouldn’t have to learn two integrations to make it. Paystack routes each call to the right rail — and records why.
Cost-optimized · peer-to-peer · no custody
Trust-optimized · internal ledger · 100% reversible
Card acceptance runs on either rail at interchange + 2.00% + $0.30, with interchange passed straight through. Inbound ACH pull is $0.75 flat.
See full pricing →CFOs don’t want an AI assistant. They want an AI assistant they can stop. SafetySwitch is the operator console — same data surface the auditors see.
Agents act within bounds that you set. You can pause everything with one click.
| VFP ID | Vendor | Amount | Release | State |
|---|---|---|---|---|
| VFP-7D4C-11A2 | Acme Roofing LLC | $1,200 | T+3d 14h | armed |
| VFP-88E1-0934 | Greenleaf Landscaping | $420 | T+5d 02h | armed |
| VFP-AA02-2CC5 | Relay Logistics | $2,875 | T+6d 18h | armed |
↳ Every action is reversible inside the audit window. Pausing halts release — held funds stay custodial until you resume or refund.
Paystack ships as a Model Context Protocol server. Point Claude Desktop, Cursor, or your own runtime at it — scopes, rate limits, and reasoning logs come for free.
# 1. Install the Paystack MCP server
mcp install codelucent/paystack
# 2. Let your agent use it
> initiate_escrow_payout(
amount: 5000,
vendor: "acme-roofing-llc",
priority: "disputable",
reason: "emergency-repair"
)
→ { vfp: "VFP-7D4C-11A2", state: "held", releasesAt: "+120h" }POST /v1/escrows
Authorization: Bearer psk_live_...
{
"amount_cents": 120000,
"counter_party": "acme-roofing-llc",
"rail": "custodial",
"audit_window": "120h",
"reasoning": {
"policy": "maintenance.repair",
"confidence": 0.94,
"agent_id": "agent-001"
}
}Agents choose: fast peer-to-peer ACH, or custodial escrow with a reversible audit window. Same API, different posture.
Every charge carries its policy, confidence, and the agent that authorized it. Compliance reads the same record operators do.
Per-agent limits, per-counter-party blocklists, and a single operator kill switch. Pause every pending escrow in one click.
Expose Paystack as a Model Context Protocol tool to Claude, Cursor, or any MCP-aware agent — with scope and audit baked in.
The 120-hour window isn't a bug. It's where disputes surface, receipts clear, and wrong agents get undone.
FBO structure, SOC2-aligned controls, and reversal flows that match the 2026 agentic-commerce rules.
Every escrow produces a Verified Future Payment. Vendors search their ID and see the funds sitting in the buffer — no phone calls, no “the check is in the mail” ambiguity.
A VFP is a cryptographic receipt that the funds exist. Enter any ID to see its current state in the escrow buffer.
Try or
The same infrastructure serves an engineer wiring up recurring collections and an autonomous agent paying a vendor at 3am. Pick the rail by urgency and ticket size — not by which one your processor happened to support.
Collect and disburse over the ACH network at same-day, next-day, or standard speed. Flat fee per transaction, no percentage, no cap to negotiate.
Settles the same business day inside the NACHA windows, up to $1,000,000 per transfer. Credits and debits both.
T+1 settlement for payroll, scheduled AP, and distributions — the correct default for money with a known date.
1–3 business days, no per-transfer network ceiling. The cheapest rail for high-volume recurring collections.
Hosted capture that keeps card data off your servers, stored payment methods, Apple Pay and Google Pay, interchange passed through at cost.
RTP, FedNow, and push-to-card. Seconds, 24/7/365, weekends and bank holidays included.
An autonomous agent pays another agent, a vendor, or a person — under caps enforced at authorization, into reversible custody, with a per-agent audit record.
Paystack is US payment infrastructure from Codelucent Technologies, LLC. One REST API covers ACH payment processing at $0.75 flat, credit and debit card acceptance at interchange + 2.00% + $0.30, instant payouts over RTP and push-to-card at 0.95% capped at $10.00, and custodial escrow. The same endpoints are exposed over the Model Context Protocol so AI agents can transact under hard spending caps.
A fixed $250/month platform fee that is never discounted by volume, plus per-transaction fees: $0.75 for standard and inbound ACH, $1.50 for same-day ACH, 0.95% capped at $10.00 for instant payouts, and interchange + 2.00% + $0.30 for cards. Bank validation is $2.00, account activation $50.00 one time, and ACH returns $25.00.
Standard ACH, same-day ACH, credit and debit cards including Apple Pay and Google Pay, instant payouts over RTP and FedNow, push-to-card, and wires. All from one API, selected by a field on the request rather than a separate integration per rail.
Yes. Paystack runs a Model Context Protocol server so an agent calls payment tools directly, and enforces per-agent per-transaction, daily, and monthly spending caps, counterparty blocklists, and an operator kill switch inside the authorization path. There is no surcharge for AI-initiated transactions.
No. Paystack originates through sponsoring bank partners, so you are not negotiating an origination agreement, building NACHA file transmission, or maintaining SFTP batch delivery.
Integrations take one engineer one afternoon. The Trust Center explains what you’re connecting to, and why it won’t page you at 2am.