Infrastructure should make the connection clearer.
CamelPay is an API connector that helps applications work with a user’s own supported payment-provider account.
Built to connect, not to replace.
People and businesses already have payment accounts. An application may need permission to request a collection or payout through one of those accounts. CamelPay provides a defined connection layer for that work.
The product keeps the roles explicit: the app requests access, the user authorizes an account, CamelPay validates and routes supported operations, and the provider controls execution and settlement.
Practical tools. Visible boundaries.
The CamelPay codebase includes a Go API, a Next.js workspace dashboard, developer documentation, and Python CLI/MCP integrations. Each interface is grounded in the same API contract.
Provider credentials, money movement, and payment outcomes remain on the provider side of that boundary.
Explore developer toolsSee what’s supported today.
Review exact provider routes before planning an integration.