OpenPayd: brokerage payments, virtual IBANs and fiat–stablecoin infrastructure

OpenPayd supplies business payment and account infrastructure for brokerages, fintechs and digital-asset businesses. Its brokerage proposition combines investor-specific pay-in identifiers, currency conversion and outgoing payments with API-based reconciliation. It can sit between a trading platform’s funding interface and the payment network. The provider’s account contract and the broker’s own customer-money structure remain separate parts of that design.[1]

The Linked vIBAN contract defines an internal Master Account reference. It creates neither an investor account nor an investor contract with OpenPayd, and cannot satisfy the broker’s own client-money or safeguarding requirements. The business retains reconciliation, customer-service and compliance responsibilities.[7]

The API uses HTTPS and a client-credentials authentication request to obtain a bearer token. Sandbox and Production use different credentials. Most requests also carry an account-holder identifier, so a platform must select the correct account context as well as authenticate. OpenPayd expressly requires credentials and tokens to remain out of client-side code and source repositories.[20]

Webhooks cover pay-ins, payouts, internal transfers, exchanges, returns, fees and account-status changes. The receiver acknowledges events with a successful HTTP response. The published retry policy uses exponential backoff for up to 24 hours for specified timeout, throttling and server-error responses; it does not promise retries for every failed response. Reconciliation should therefore be able to recover transaction state after a missed event.[21]

OpenPayd signs webhook payloads and publishes verification examples using a public key downloaded from the Dashboard. Signature checking establishes message authenticity. It should precede any automated change to a brokerage funding balance; receiving a syntactically valid callback alone is insufficient evidence that OpenPayd sent it.[22]

OpenPayd’s pricing FAQ says every offer is bespoke. The reviewed public material contains no general numeric tariff for accounts, virtual IBANs, FX or individual payments. A cost comparison needs the proposed account and payment mix, expected volume, currencies and digital-asset use cases. A quote for fiat collections should not be treated as including a separate stablecoin arrangement.[8]

SEPA Direct Debit requires enablement, with settlement intervals and reserves agreed commercially. Refunds and chargebacks can follow collection, so the per-collection fee does not describe the entire cash-availability model.[7]

The onboarding FAQ describes an introductory discussion, document collection, compliance review and a call between compliance teams. Its shortest stated timeframe is two weeks, explicitly dependent on documentation arriving promptly. This is a vendor estimate for onboarding, not a guaranteed delivery date for a broker’s full integration, migration and customer launch.[9]

The April 2026 terms permit OpenPayd to require its own compliance approval and approval from banking partners. End-user payment flows require express agreement. The implementation plan therefore needs an accepted funds-flow model before the business presents virtual payment identifiers or starts using the production account for customer activity.[6]

OpenPayd’s Information Security Statement describes separate production and non-production environments, encrypted data handling, annual continuity testing and independent penetration testing. It reports ISO/IEC 27001 and ISO/IEC 20000-1 certifications and PCI DSS 4.0.1 compliance. These are the provider’s statements; customers can request supporting executive evidence or attestations. The reviewed page does not establish the exact scope or expiry of a certificate delivered for a particular contract.[28]

Direct customers obtain technical help through the platform’s Help Centre and a dedicated Customer Success Manager. An investor using a brokerage that happens to use OpenPayd is directed to that brokerage for assistance. That allocation should be reflected in the app’s payment-help journey, particularly when the investor recognises OpenPayd on a bank statement but has no direct OpenPayd account.[10]

The complaints policy promises acknowledgement within two working days and normally a final reply within 15 working days, with 35 working days as the stated maximum. These are complaint-handling periods, not production-incident response targets. Referral to the UK Financial Ombudsman Service or Malta’s financial-services arbiter depends on eligibility and the contracting arrangement.[11]

The general terms define an OpenPayd Account as non-interest-bearing e-money. They exclude deposit-scheme protection on OpenPayd’s failure and describe safeguarding instead. The terms also specify that conversion-stage funds are outside that safeguarding and prohibit using the account to satisfy the customer’s own client-money or safeguarding obligations. A broker therefore needs a separate legal basis for its own obligations; a pooled payment balance is not enough.[6]

The AMF entry was published on 9 July 2026 and identifies the 24 June date as the intended start of French services. OpenPayd separately announced completed MiCA authorisation on 24 June. Its general website footer still uses the older VFA description for OP Digital. This profile gives precedence to the matched current MiCA record for European crypto services and retains the website’s separate geographic offer restrictions.[16][17]

OpenPayd says it was founded in 2018 by Dr Ozan Ozerk. The present group spans fiat-payment and digital-asset entities; OpenPayd Holdings Limited is identified as the ultimate holding company. The business brand and the service supplier should both be recorded in a procurement file, because the relevant entity changes with geography and product.[17][13]

Companies House records SettleGo Solutions Limited as active, company 09570221, incorporated on 30 April 2015. It used the name Facekart Limited until February 2018. The former name can therefore appear in older corporate records and contracts relating to this UK company.[19]

Operator

OpenPayd group; service entities include SettleGo Solutions Limited and OpenPayd Financial Services Malta Limited.

Service scope

B2B accounts, virtual payment identifiers, payment APIs, treasury FX and separately contracted digital-asset services.

Customer types

Brokerages; Fintechs; Payment businesses; Digital-asset businesses; Platforms; Corporate treasury teams

Delivery

API; SaaS

Pricing publication

Quote only

Platforms

OpenPayd API; OpenPayd Dashboard; Virtual IBANs; Pooled Accounts; Open Banking; Stablecoin infrastructure

Integrations

REST API; OAuth client credentials; Signed webhooks; Faster Payments; CHAPS; SEPA Credit Transfer; SEPA Instant; SWIFT; ACH and wire routes; Circle Payments Network

Pricing scope

Bespoke quotation; service fees, FX treatment and applicable third-party costs follow the agreed arrangement.

Implementation

Agree the funds flow and contracting entity, complete compliance and any partner approvals, then integrate authentication, verified events and reconciliation.

Support

Direct-client Help Centre and dedicated Customer Success Manager; end users contact their platform. Complaint handling has separate published timelines.

Permissions and regulatory scope

UK entity disclosure references FCA 900483. Matched Lithuanian EMI entry for Malta C75580 and AMF MiCA passport entry for OP Digital; the group’s Canadian MSB disclosure is attributed.

Provider metadata checked 21 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 13Source 14Source 15Source 16Source 18Source 19Source 20Source 22Source 23Source 24Source 27

OpenPayd’s 25 August 2026 announcement says its Circle Payments Network integration is live. The described model uses stablecoins behind fiat payment flows, with EUR-to-BRL and GBP-to-MXN as operating examples. Circle Technology Services runs the coordination network; the announcement says it neither holds customer funds nor manages their accounts. This supports a current network integration claim, not universal instant settlement for every OpenPayd currency or beneficiary.[18]

The API documentation distinguishes the Open Banking payment-status event from the completed pay-in event. The latter is sent when funds have been credited to the account. A platform can use the payment identifier to track the payer’s journey, then reconcile the credited transaction and account before posting the funded balance. The two messages describe different steps in the flow.[24][23]

Two public documentation gaps affect implementation. The currency and payment-type matrices have older update stamps and distinguish receipt, payout and conversion availability. Their broad lists should not be presented as a single current account entitlement. Obtain the enabled currencies, beneficiary destinations, limits and cut-offs for the actual production contract.[26][27]

The older Linked Clients guide describes distinct parent-child account holders. Current Linked vIBAN terms instead define an internal identifier. The approved contract must resolve which documented model applies before the platform labels its customer’s facility.[25][7]