IFX ibanq
IFX multicurrency payment-account infrastructure with named IBANs, subaccounts and API access.
Supplier popularity25%By OpenPayd
OpenPayd Virtual IBANs
Named client payment identifiers allocated under pooled accounts for payment attribution and reconciliation.
The offering
What OpenPayd Virtual IBANs does
OpenPayd Virtual IBANs allocates named payment identifiers to underlying clients after the business has established its pooled accounts. The offer uses an API to associate a virtual IBAN with a linked client, currency and account name, helping the buyer identify incoming and outgoing activity. OpenPayd explicitly presents virtual IBAN allocation in its gaming infrastructure offer.
Treat this as client payment allocation infrastructure. The page describes identifiers under pooled accounts; it does not establish a separately owned bank deposit account for every player or provide the operator’s gaming balance ledger. Agree accepted fund ownership, eligible client types, currencies, incoming routes and any player-money protection arrangement before onboarding. Map each identifier to the correct client record and verify transaction evidence, corrections and exceptions with the finance team.
Who should explore it?
Approved operator payment and finance teams requiring client-level payment attribution under pooled account infrastructure.
- Attribute approved incoming transfers to the correct client record
- Reconcile client-related payment activity against an operator ledger
Documented capabilities
- Named virtual IBAN allocation
- Linked client and currency parameters
- Pooled account structure
- Incoming/outgoing transaction visibility
- API access
Reported in the linked public sources. We have not independently tested these capabilities.
Product details
- Client allocation job
- Named virtual payment identifiers for underlying clients and payment reconciliation.Source
- Underlying structure
- Virtual IBANs are allocated after pooled accounts are opened; separately owned client bank deposits are not established by this offer.Source
- Currency scope
- The API links an identifier to a client and currency; enabled currencies and underlying accounts must be agreed.Source
- Allocation interface
- API allocation using linked-client, currency and account-name information.Source
- Payment attribution
- Named identifiers support client-level visibility over incoming and outgoing transactions.Source
- Accepted fund flows
- The gaming offering includes virtual IBAN allocation; service-specific entity, client and fund-flow onboarding remains necessary.Source
Delivery & commercial details
- Delivery & integration
- Open approved pooled accounts, agree client and fund scope, then allocate virtual IBANs through the API. Validate identifier-to-client mapping, currency enablement and transaction reconciliation before using player-related flows.Source
- Pricing
- Request account and identifier charges, transfer/FX fees, volume tiers and exception terms for the selected client allocation design; no complete tariff is published on the reviewed page.
Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.
Buyer questions, answered
Does each virtual IBAN establish a separate player-owned bank account?
The product describes allocating named virtual IBANs after opening pooled accounts. Confirm legal account ownership and player-money arrangements in the contract; the identifier itself does not establish an individual bank deposit account.
SourceHow is this different from a corporate account?
Virtual IBANs allocate identifiers to underlying clients for transaction attribution. Corporate Accounts is separately marketed for business funds and spending; client allocation requires its own approved design.
Source