05 — Infrastructure
API & infrastructure
Embed payment and settlement capabilities into your own workflows and products.
What it is
Where a capability belongs inside a client’s own product or back office, it is exposed programmatically under the same onboarding, screening and approval model that governs it when instructed directly.
How it works
4 steps, in order.
Each step gates the next. Nothing downstream begins until the step before it has completed.
- 01
Scope and design
The capabilities to be exposed, the flows they support and the responsibilities on each side are defined before any access is issued.
- 02
Credentialed access
Access is issued under the agreed framework, scoped to the approved activity rather than to the platform as a whole.
- 03
Integration and testing
Integration is validated against the agreed operating procedures, including how exceptions and rejections are handled.
- 04
Controlled activation
Capabilities are enabled for agreed activity following successful checks, and remain subject to ongoing review.
POST /v1/paymentsHost: api.example-institution.testAuthorization: Bearer <scoped-token>Content-Type: application/json { "reference": "INV-4821", "source_account": "acct_operating_gbp", "destination": { "beneficiary_id": "ben_approved_004", "currency": "USD" }, "purpose_code": "supplier_payment", "idempotency_key": "6f1c2a90-..."}
Who it is for
Availability depends on the client, use case, jurisdiction, currency, payment route, banking and liquidity arrangements, and successful compliance review.
Who it is for
When you would use this.
For platforms whose users expect payment or settlement to happen inside the product rather than beside it.
- Fintech platforms embedding payout or settlement into their own flows
- Marketplaces distributing funds to sellers or contractors
- Software businesses adding payment capability to an existing workflow
Important information
Technical documentation, environments and credentials are provided under a signed agreement following onboarding. No public API is offered through this website.
Product availability is subject to onboarding, jurisdiction, eligibility and the final operating model. Regulatory and partner details will be published only after verification.
Start a conversation
Let’s design a better payment flow.
Tell us what you need to move, where it needs to go, and how your organisation operates.
- 01
Payments & FX
Markets, currencies and intended transaction flows
- 02
Stablecoin settlement
Eligible fiat-to-USDT use cases and operating requirements
- 03
API & partnerships
Infrastructure, integration and commercial enquiries