OpenPayd

• Name: OpenPayd
• URL: https://www.openpayd.com/
• Category: embedded financial infrastructure / regulated fiat-and-stablecoin settlement control-plane company / API-led accounts-payments-FX operator
• Tags: ethereum-ecosystem
• Summary: OpenPayd belongs in companies/, not just projects/, because the durable dependency is a named company operating the account, payment, FX, virtual-IBAN, linked-client, and stablecoin workflow shell that customers inherit. The useful question is not only what API does OpenPayd expose? but which regulated group entities control onboarding, account issuance, beneficiary permissions, supported currencies, webhook truth, fiat-crypto conversion, and the legal perimeter behind the stack?
• What it does:
  • Operates a single API-led platform for accounts, payments, FX, virtual IBANs, and stablecoin-linked flows, with dashboard and OTC-desk access alongside the API
  • Lets platforms create multi-currency accounts, run payin and payout workflows, and access instant FX settlement across supported currency pairs
  • Supports unlimited named virtual IBANs plus pooled-account and reconciliation workflow for downstream customer funds operations
  • Onboards linked business or individual customers in a parent-child model so those customers can hold accounts, maintain beneficiaries, and transact within the OpenPayd environment
  • Packages stablecoin receive / hold / convert / send flows and fiat-crypto conversion through dedicated digital-asset entities inside the broader OpenPayd group structure
  • Exposes sandbox, account-creation, currency-support, and webhook surfaces that make the company-run operating shell more important than any one product page
• Key claims:
  • The homepage frames OpenPayd as rail-agnostic infrastructure that combines traditional finance and digital assets through one API
  • The site says OpenPayd processes more than $180 billion annually, serves 1000+ clients, maintains 99.99% platform uptime, and supports 5M+ connected accounts; those are useful vendor scale signals rather than independently verified measurements
  • The stablecoins materials say businesses can receive, hold, convert and send stablecoins globally and embed stablecoins into payment flows just like fiat
  • The on/off-ramp materials say clients can trade major digital assets through the API, dashboard, or OTC desk with instant settlement on a fully regulated platform
  • The linked-clients docs show that OpenPayd explicitly models parent-child admission and downstream-customer autonomy inside the same operator shell, which is strong evidence that the real control surface is organizational and workflow-driven
  • The legal and group-overview materials explicitly separate fiat-payment services from digital-asset services across FCA-, MFSA-, and FINTRAC-regulated entities, which is exactly why the company boundary matters more than a generic banking API label
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest primary materials are OpenPayd’s official site, API landing pages, developer docs, and legal/group pages; the primary-source bundle remains ../whitepapers/openpayd-primary-sources-2026-04-30.md.
• Sources:
  • https://www.openpayd.com/
  • https://www.openpayd.com/api/
  • https://www.openpayd.com/stablecoins/
  • https://www.openpayd.com/virtual-ibans/
  • https://www.openpayd.com/multi-currency-accounts/
  • https://www.openpayd.com/on-off-ramp/
  • https://www.openpayd.com/legal/openpayd-group-overview/
  • https://apidocs.openpayd.com/
  • https://apidocs.openpayd.com/docs/linked-clients
  • https://apidocs.openpayd.com/docs/create-payment-account
  • https://apidocs.openpayd.com/docs/supported-currencies
  • https://apidocs.openpayd.com/docs/webhooks

Internal linkages

• Project-layer alias note: openpayd.
• Useful adjacent company reads: bridge-xyz, bvnk, and aquanow.
• Cleaner contrast where the question becomes lower-layer payment initiation rather than one regulated operator stack: open-payments.

Protocol / company boundary

• OpenPayd does not read like a neutral protocol or standalone network whose deployed mechanics explain the main dependency.
• The analytically important surface is the company-run operating shell that packages customer admission, account issuance, beneficiary handling, virtual-IBAN provisioning, payment routing, FX conversion, stablecoin enablement, webhook state, and regulated-entity perimeter inside one inherited vendor workflow.
• That is why OpenPayd belongs in companies/: the real leverage sits with the entity group that controls the workflow graph and legal operating shell, not with an abstract product label.

Control surface

• Practical authority sits in partner onboarding, linked-client admission, account and virtual-IBAN issuance, beneficiary and payment permissions, currency and rail support, FX routing, webhook and lifecycle truth, fiat-crypto conversion policy, and which regulated group entity a customer relationship actually lands inside.

• The sticky dependency is workflow memory: once a platform builds around OpenPayd-managed accounts, linked clients, reconciliation state, beneficiaries, webhook handling, and stablecoin conversion flows, the lock-in is to the company-run operating shell rather than to a generic accounts or payments API.

• Read OpenPayd as a regulated operating boundary first. The API is distribution; the real control surface is the company shell behind account, settlement, and compliance workflow.

• Last reviewed: 2026-08-06 UTC