Now self-serveAccess PayOS data to make better payment decisions, no sales call needed.Start building →

Integrate the way that suits you.

From a single agent to a global enterprise, pick the route that fits your stack and compliance posture. Every PayOS service is available on every route.

API / SDK / MCP Server
Call PayOS directly
Stripe Vault & Forward
Cards stay at Stripe
PCI Proxy
No PCI scope needed
Same operations, same results, every route

Three routes. One platform.

Choose how card data reaches PayOS. What you get back is identical.
↓
Direct
API / SDK / MCP Server

Call every PayOS service over one REST API, with SDKs where we publish them and an MCP server for AI agents.
↓
Stripe
Stripe Vault & Forward

Run PayOS card services on cards already vaulted with Stripe. Your systems never handle the card number.
↓
PCI
PCI Proxy

Offer card services without PCI compliance. Card data stops at the PayOS edge; tokens and data reach you.
01Direct

API / SDK / MCP Server

Call PayOS yourself. Every service on the platform, one REST API, SDKs where we publish them, and an MCP server for AI agents.

1
Get your keys
Sign up, fund a balance, and get sandbox and production keys in minutes.
2
Call any service
One REST API covers every data product. Webhooks deliver async results.
3
Let agents connect
AI agents call the same services through the PayOS MCP server.
Best for engineering teams and AI agents
Your appAPI · SDK
Request
PayOSEvery service
Response
Your agentMCP server
Explore Direct integration
02Stripe

Stripe Vault & Forward

Run PayOS card services on cards already stored with Stripe. Stripe forwards the card on your instruction, so your systems never touch it.

1
Cards stay at Stripe
Nothing migrates. Cards remain vaulted exactly as they are today.
2
Stripe forwards to PayOS
You trigger a forward; Stripe sends the card over its certified path.
3
Data comes back
Verification, BIN, PAR and every card signal return to you.
Best for cards already in a Stripe vault
YouTrigger forward
Instruct
Stripe vaultHolds the card
Forward
PayOSReturns data
Explore Stripe integration
03PCI Proxy

PCI Proxy

Offer card services without being PCI compliant. Card data terminates at the PayOS edge; only tokens and data reach your systems.

1
Card enters at the edge
A PayOS-hosted field or proxied call captures the card, never your servers.
2
The card number stops there
It is tokenized at the edge. Your stack stays out of PCI scope.
3
You get the full answer
Every card service runs on the token and results flow back as clean data.
Best for card data without PCI scope
CustomerEnters card
Capture
PayOS edgeTokenizes
Token
Your stackNo PCI scope
Explore PCI integration

Which route fits you?

Tell us where your cards live today and we will map the shortest path to running PayOS on them.