Developers
Build on the Payscape APIs.
Embed payment accounts, IBANs, cards and payments into your product — white-label, API-first, ready to run.
What you can build
Five capabilities, one integration.
Open accounts and assign IBANs
Open payment accounts and assign dedicated virtual IBANs programmatically — one per customer, payer or property.
Create and control cards
Create virtual or physical debit cards, set spend limits, freeze, replace and manage card controls via API.
Move money — SEPA pay-in and pay-out
Receive SEPA Credit Transfers and SEPA Instant payments; send outbound transfers individually, in bulk or on a schedule.
Provision cards to Apple Pay and Google Pay
Push cards to the device wallet using the in-app provisioning API — no separate scheme enrolment required.
Onboard and verify customers
Run ID&V, KYC and KYB checks at onboarding and retrieve screening and risk outcomes as structured API responses.
Handle rule-based splits
Configure commission splits, payout rules and fund-routing logic — execute them automatically on inbound payment events.
The API
A REST API covering the full embedded-finance stack.
The Payscape API is a single REST interface across accounts, cards, customers, corporates, in-app provisioning and credit transfers. JSON request and response bodies throughout. Standard HTTP status codes and predictable error shapes.
/v1/customersCreate, retrieve and manage customer records and KYC/KYB status
/v1/accountsOpen payment accounts, assign IBANs, query balances
/v1/cardsIssue cards, set controls, retrieve secure card data
/v1/credit-transfersSend and receive SEPA CT and SEPA Instant transfers
/v1/corporatesManage entity hierarchies and consolidated balances
/v1/provisioningPush cards to Apple Pay and Google Pay wallets
# Create a customer and open a payment accountPOST /v1/customersAuthorization: Bearer {token}# Request body{"type": "individual","email": "jane.smith@example.com","first_name": "Jane","last_name": "Smith"}→ 201 Created{"id": "cus_01JNKX4R8VZWP...","status": "pending_verification","iban": "IE29PSCP93115212..."}
Key concepts
What you need to know before you build.
Authentication
All requests are authenticated with a bearer token. Tokens are scoped and short-lived. Refresh via the token endpoint.
Webhooks and events
Subscribe to events — account.created, card.issued, transfer.completed — and receive signed payloads to your endpoint in real time.
Sandbox environment
A full sandbox with simulated accounts, cards and payment flows. No real money. Test the complete integration before going live.
Versioning
API versions are date-stamped. Breaking changes are introduced in a new version with advance notice and a supported migration period.
Access
API or portal — your choice.
Build on the APIs
Embed accounts, IBANs, cards and payments directly into your product. REST APIs with an OpenAPI spec, webhook events for every state change, and a full sandbox to test against — your users stay in your interface throughout.
View the API referenceOperate from the portal
The same capabilities — opening accounts, issuing cards, sending payments — are available from the Control Cloud web interface. No integration required. Some teams build first, then embed; others operate from the portal throughout.
Request a demoSupport
A team of experts to help you integrate.
Payscape's integration team works directly with developers: from your first API call to production go-live. They know the edge cases, the compliance requirements and the platform well enough to unblock you fast. Reach out before you start, or when you're stuck.
Start building.
The API reference covers every endpoint, parameter and response shape. A full sandbox is available with no setup required.
