Build payment flows
Payments API
Accounts, payment requests, collections and transactions. Endpoint schemas and scopes in one reference.
Open API referenceDevelopers / Start here
Your code.Regulated money.
Connect your software to Quantoz accounts and payments. Find the documentation, access model and permissions that fit what you're building.
01 / Choose your route
Find the docs.
Start building.
Build for AI
Agentic Stack
Connect agents through MCP. Use x402 to pay for or sell digital resources.
Explore agentic docsManage your access
Quantoz Portal
Your accounts, balances and transaction history. Create and manage scoped API keys.
Open the PortalOperating your own token infrastructure?
Nexus platform documentation covers the separate technology product for your own environment.
Service availability
Check live availability and incident updates.
02 / Integration models
For your business.
Or for your customers.
Direct integration
Operate your own account.
Your business
Your software
You authenticate and operate the accounts under your own customer profile.
Embedded integration
Bring payments into your product.
Customer consent per profile
Your product
Your backend authenticates. Each customer authorises access to their profile through explicit consent.
Choose the model around who owns the account and who gives the payment instruction.
Read the integration guide03 / Access & permissions
A clear path.
Controlled from the start.
- 01 / Agree the service
Set up your account.
Onboarding and your agreement define the available functions.
- 02 / Create your key
Choose the permissions.
Create a key in the Portal with the scopes your integration needs.
- 03 / Test the full flow
Prepare for production.
Validate requests, payment outcomes and callbacks before going live.
Agreed service+Key permission
Both are required for an API action.
04 / From request to completion
Build beyond
the first response.
- Your application
Create the request
Payment link or QR
- The payer
Complete the payment
Follow the payment flow
- Quantoz
Confirm the payment
Payment outcome recorded
- Your callback
Update your system
Reconcile the result
One reference connects the flow. Include your reference and callback URL to match the payment event to the original request.
Confirm the payment outcome before fulfilling an order.
Payment request reference05 / Money in
Your own funds.
Or a customer's payment.
Funding
Add money from your bank.
Your bank account
Collections
Receive money from a payer.
Payer's bank account
Collections and other business functions require the relevant service agreement.
Explore payments & collectionsCommon questions
Before your
first call.
Which scopes should my key have?
Use only the permissions needed for the job. ReadOnly supports reporting; AccountManage covers administration. InternalPayment permits payments within your profile. Adding ExternalPayment permits payments to other Quantoz accounts. Each endpoint lists its required scope in the API reference.
What does an embedded integration need?
Partner onboarding, a commercial agreement, appropriate act-on-behalf scopes and explicit customer consent per profile. Partner delegation also requires a whitelisted static backend IP. Start with the integration guide.
Where do I start with an AI agent?
Follow the account and key setup, then the MCP quickstart. The agentic payments solution explains the business flow and owner controls.
How do accounts and blockchain wallets fit together?
The Quantoz Wallet accesses your regulated e-money account. EURQ and USDQ tokens are held in a separate compatible blockchain wallet. Explore the digital money platform to see how accounts, tokens and controls connect.
Ready to connect?
Bring your use case.
Build with Quantoz.
Talk to us about the account, integration model and access your product needs.