Skip to main content
HighRiskPaymentProvider.comPayment provider reviews
Nium Multi Currency Accounts

Company overview

About Nium

What the company provides

  • Processor
  • Payouts
  • Foreign exchange provider
  • Card issuer
  • Issuer processor
  • Payment account provider
  • Payment account technology provider
  • Payout technology provider

Available countries, payment methods, data access, contracts and funds handling depend on the selected product.

Nium provides regulated cross-border payment infrastructure through jurisdiction-specific group entities and financial partners.

Its products include multi-currency payment accounts, global payouts, foreign exchange, physical and virtual card issuing, and B2B travel cards for online travel agencies, airlines and hotels. Nium or the applicable program bank can receive, safeguard and move client funds for enabled account, payout and card products. Nium does not provide a universal card-acquiring relationship, merchant acceptance account or card MID.

Founded 2014nium.comUpdated Aug 15, 2026

Selected product

Nium Multi Currency Accounts

Multi-currency payment accounts provided by a Nium regulated entity

Merchant account & merchant review

  1. Account & contracting

    Varies by agreement

  2. Payment-services client & account activation

    Nium approves the payment-services client and requested account configuration

    KYC, KYB, financial-crime, business-model and funds-flow review applies before the payment account, identifiers, currencies and bank rails are enabled. This reviews the payment-services client and account configuration; it is not a merchant payment-acceptance decision.

Primary legal entity

Jurisdiction
Singapore
Company type
Private limited company

Legal entities by jurisdiction

9 legal entities across 7 jurisdictions

  • United Kingdom3 entities
  • Australia1 entity
  • Lithuania1 entity
  • Malta1 entity
  • Netherlands1 entity
  • Singapore1 entity
  • United States1 entity

Operating scale

Licences and registrations
≥40 licences authorisations and registrations
Payout country reach
≥190 payout countries and territories
Payout currency reach
≥100 payout currencies
Real time payout reach
≥100 real time payout markets
Card issuing market reach
≥30 card issuing markets

The legal entity supplying a product can differ by product and country.

Product portfolio

Nium products

Compare regulated payment accounts, payouts, card issuing, and institutional FX and liquidity by account setup, approval, payment or data flow, and contract terms.

Nium Multi Currency Accounts

Role in this product

  • Payment account provider
  • Payment account technology provider

Receive approved pay-ins, maintain available balances in supported currencies, convert funds and fund payouts or issued cards through a Nium payment-account structure.

A virtual account number is a notional identifier linked to a settlement account and is not a separate bank account. The relevant Nium entity or, in the United States, the program bank controls custody and regulated payment services.

Related services
Business accountsCurrency conversion
Features
BankingCurrency managementOnboardingUnderwritingPricingReconciliationReportingCompliance

Nium Global Payouts

Role in this product

  • Payouts
  • Source account and available balance
  • Payout technology provider

Send funded payouts to bank accounts, cards and wallets across 190-plus countries and territories and 100-plus currencies, with real-time delivery available in 100-plus markets.

The applicable Nium entity or program bank executes the payout through local banks, card networks, wallets and other payment rails; the exact route, timing and funds custodian are jurisdiction- and corridor-specific.

Related services
Currency conversionCustomer payouts
Features
PayoutsCurrency managementOnboardingUnderwritingPricingReconciliationReportingCompliance

Nium Global Card Issuing

Role in this product

  • Issuer processor

Launch approved physical and virtual Visa or Mastercard card programs in 30-plus markets, with configurable limits, rules and merchant-category controls.

Cards use the approved Nium account, prefunded balance, collateral or other contracted authorization model. Issuing does not give the client a card-acceptance merchant account or MID.

Related services
Card issuingCurrency conversion
Features
IssuingCurrency managementOnboardingUnderwritingPricingReconciliationReportingCompliance

Nium Travel Virtual Cards

Role in this product

  • Issuer processor

Issue controlled virtual cards for online travel agencies, airlines and hotels to pay airlines, accommodation providers, suppliers, partners and employees.

Official travel material describes 20-plus issuing currencies, acceptance in 150-plus countries, single- and multi-use controls, booking-reference reconciliation and optional travel-specific UATP or charge-card structures. This is a B2B supplier-payment product, not hotel guest checkout acquiring.

Related services
Card issuingCurrency conversion
Features
TravelCurrency managementOnboardingUnderwritingPricingReconciliationReportingCompliance

Nium Global FX

Role in this product

  • Foreign exchange provider
  • Foreign exchange execution

Convert supported balances for account funding, payouts and card programs through Nium's contracted foreign-exchange service.

Currency pairs, quote validity, markup, execution entity, cut-offs and whether conversion is automatic or instructed are product- and jurisdiction-specific.

Related services
Currency conversion
Features
Currency managementOnboardingUnderwritingPricingReconciliationReportingCompliance

Selected product

Nium Multi Currency Accounts

Related services
Business accountsCurrency conversion
Features
BankingCurrency managementOnboardingUnderwritingPricingReconciliationReportingCompliance

Payment account, safeguarding & payment rights

Who provides and holds the payment account, how funds are safeguarded and which incoming, outgoing and reconciliation functions are contracted.

01 · Role in this product
Payment account provider · Payment account technology provider
02 · Account & contracting
Varies by agreement
03 · Eligibility & approval
Varies by agreement
04 · Settlement & funds
Varies by agreement

Selected product: Nium Multi Currency Accounts.

Payment accounts

Nium Multi Currency Accounts: account balance, identifiers & bank rails

Review who provides the regulated payment account, which named or virtual identifiers are linked to it, how balances are safeguarded and which incoming, refund, payout or sweep routes are enabled.

Selected product: Multi-currency payment accounts provided by a Nium regulated entity

Included in Nium Multi Currency Accounts

Features included with this product.

Solutions
Business accountsCurrency conversion
Capabilities
BankingCurrency managementOnboardingUnderwritingPricingReconciliationReportingCompliance

Payment account, safeguarding & bank rails

Who approves and provides Nium Multi Currency Accounts, where its balance is safeguarded, and which bank rails can receive or send funds.

Included

Reporting & reconciliation

Nium provides transaction reports and reconciliation data for Multi-currency payment accounts provided by a Nium regulated entity through its reporting channels.

Operations data

Which transaction, usage and billing data can finance and operations reconcile?

Reports · Transaction, provider, feature-usage and billing reports

Available
Yes
Access
  • Nium Portal
  • Nium APIs
Scope
  • Account and available balance
  • Pay in and payout status
  • Beneficiary and corridor
  • Foreign exchange
  • Issued card and spend controls
  • Travel booking reference reconciliation
External record boundary
Bank, card-network, supplier and beneficiary-account records remain external records for the relevant leg of the transaction.
Availability
Depends on the product, payment rail, provider response, card-network clearing, beneficiary delivery and configured API or Portal workflow.

Reconciliation

Multiple-provider and multiple-source reconciliation coverage

Automated matching
Yes
Multiple data sources
Yes
Product name
Nium Portal and API reporting
Status discrepancy handling
Nium transaction and account reporting should be reconciled with the client's funding bank, beneficiary bank, card network, travel supplier or other external rail. A transaction state does not convert a virtual account number into a separate bank account or Nium into the client's merchant acquirer.
Product account · Multi-currency payment accounts provided by a Nium regulated entity

What is required to activate this product?

Nium approves the payment-services client and requested regulated account, identifier, currency and rail configuration.

Company eligibility

Owner, director and operating-location requirements are not specified

Merchant account

Nium approves the payment-services client and requested account configuration

KYC, KYB, financial-crime, business-model and funds-flow review applies before the payment account, identifiers, currencies and bank rails are enabled. This reviews the payment-services client and account configuration; it is not a merchant payment-acceptance decision.

Product setup
Platform client acceptance
Product
Multi-currency payment accounts provided by a Nium regulated entity
01Product eligibility & acceptable use

Which businesses and uses are accepted for this product?

Product account eligibility and acceptable-use restrictions are separate from merchant-account underwriting.

Eligibility requirements

01

Eligibility information

These checks cover the client, use case and regulated service, not a card merchant account. Nium does not specify one universal approval matrix across all entities, accounts, corridors, payout methods and card programs.

02

Merchant application decision

The applicable Nium entity or program bank approves the client and requested capabilities. Product access in one licensed jurisdiction does not establish availability through every Nium entity or route.

Restricted activity

Business restrictions

Product · MCC · jurisdiction · sales practice

Product, MCC, sales-practice and jurisdiction restrictions are not specified for this product.

02Product account setup

What is needed before this product can be activated?

Company information, commercial terms and technical setup requirements for this product.

Product account setup

Open product account → agree terms → configure integration → activate

Merchant-account approval may still be required separately for live payment processing.

Processing application documents

Documents to prepare

  1. 01Corporate and beneficial owner information
  2. 02Business model and funds flow
  3. 03Requested products countries currencies and corridors
  4. 04Beneficiary or card program use case
  5. 05Origin destination and currency requirements
  6. 06Regulatory licenses when applicable

Merchant review & processing activation

  1. 01

    Identify the client, customer model, requested products, countries, currencies, payment corridors and card or travel use cases.

  2. 02

    Determine the applicable Nium regulated entity or US program bank and the permissions available for that product and jurisdiction.

  3. 03

    Complete corporate due diligence, beneficial-owner review, activity and funds-flow assessment and any end-customer onboarding required by the chosen product configuration.

  4. 04

    Agree the fee schedule, funding and safeguarding arrangement, limits, currencies, beneficiary or card-program controls and prohibited-business conditions.

  5. 05

    Integrate through the Nium API or configure the Nium Portal and exchange any required bank, network or program credentials.

  6. 06

    Test account funding, payouts, FX, card authorization and reporting paths before production activation.

Product account requirements

Account setup and activation

Application and activation requirements.

Website requirements

Required website pages, disclosures and policies are not specified

Merchant-account and processing requirements

Business, ownership, sanctions, merchant-account and processing checks are not specified

Processing onboarding tasks

The onboarding tasks performed by the provider are not specified

Before applying

Application requirements to confirm

Product account requirements, acceptable-use restrictions and activation timing are not fully specified.

Approval & restrictions

Who reviews the business and which products, jurisdictions or MCCs are excluded.

  1. 01

    Which regulated entity provides the payment account, who is the account holder and which named or virtual identifiers are enabled?

    The account entity, holder, identifier format and currencies depend on the approved configuration.

  2. 02

    Which safeguarding bank, incoming rails, refund routes, payout or sweep routes, cut-offs and balance rules apply?

    Payment-account funds handling and enabled bank rails are product- and contract-specific.

Vertical acceptance

Which high-risk verticals this provider answers for

Every row is a statement the provider publishes about a business type. Hover or focus a decision to read the original wording. A vertical with no row here is one the provider does not address.

Applies only to

B2B travel virtual cards and airline-payment structures

Vertical acceptance for B2B travel virtual cards and airline-payment structures
VerticalProvider’s position
TravelAccepted
Payment methods & countries · Multi-currency payment accounts provided by a Nium regulated entity

Where can the business process payments, and which methods are available?

Account entity, currencies, identifiers, safeguarding and enabled bank rails define payment-account reach.

Selected product

Multi-currency payment accounts provided by a Nium regulated entity

Regulated payment-account coverage

Selected product

Business applying for processing

Defined by client review, use case, funds flow and requested account configuration

Method categories

  • Bank transfer
  • Card payouts
  • Cards
  • Real-time bank payments
  • Wallets

Currencies

≥100 payout currencies

The currencies total can include several products; the number available with this product depends on the agreement.

Availability depends on

  • Selected Nium product
  • Contracting entity or program bank
  • Client and use case approval
  • Origin and destination market
  • Funding and payout currency
  • Beneficiary type and details
  • Card program and network
  • Transaction screening and limits

Nium provides the approved payment account and linked named or virtual identifiers. Account, balance, safeguarding, incoming, refund, payout and sweep rights remain configuration-specific.

01Payment-method availability

Card acceptance and card payouts

Payment-method availability depends on the selected product, legal entity, merchant country, customer country, currency, merchant category and account configuration.

Card acceptance

Card types

  • Physical
  • Virtual
  • Prepaid
  • Charge

Card brands

  • Visa
  • Mastercard

Bank payment rails

Bank methods

Bank methods by customer country are not specified

Bank-transfer rails

Bank-transfer rails by currency are not specified

Digital wallets

Wallets

Wallet availability by country and currency is not specified

Card payouts

Card payout rails

  • Supported payment card
02Countries & availability

Where can the business be registered, where is acquiring available, and where can customers pay?

Business location, merchant-account coverage, acquiring countries and customer location can differ.

Country coverage

Merchant, acquiring, customer and product countries

  1. 01

    Business location

    Where can the business applying for processing be registered?

    Defined by client review, use case, funds flow and requested account configuration

    Merchant application review
  2. 02

    Acquiring countries

    Where is merchant acquiring available?

    Contract-specific named or virtual identifiers and bank rails

    The account does not provide a card MID or card-acquiring footprint.

    Selected product
  3. 03

    Customer location

    Where can customers pay from?

    Depends on account currency, identifier format and enabled bank rail

    Across all products

Countries and payment methods

Countries and payment methods to confirm

  1. Which account entity, holder, currencies, identifier formats and bank rails are enabled?

    The payment-account configuration is product- and contract-specific.

  2. What safeguarding, balance, refund, payout, sweep, cut-off and termination rules apply?

    Funds handling and account access depend on the regulated account terms.

Pricing & funds · Multi-currency payment accounts provided by a Nium regulated entity

What does this product cost, and when are funds settled?

Payment-account pricing, safeguarding and enabled bank-rail flows

Pricing

Standard processing rate is not specified for this product

The processing rate is not specified.

Pricing method

No public rate card

01Commercial terms

What makes up the quoted price?

Review the pricing plan, pricing model, fees and contract duration.

  1. 01 · Pricing plan

    • Nium account contract pricing

Fee structure

Fees that may appear in the agreement for this product

  1. 01
    Possible fees
    May apply
    • Account and platform fees
    • Pay in fees
    • Foreign exchange rate or markup
    • Bank and third party fees

    Amounts and applicability vary by merchant agreement.

Fees requiring a quote

Amounts and waivers are not specified

monthly fee
setup fee
application fee
annual fee
gateway fee
PCI fee
batch fee
early-termination fee
monthly minimum
02Payment-account balance & safeguarding

Which payment-account balance & safeguarding terms apply?

How eligible funds are recorded in the regulated payment account and safeguarded through the configured bank structure.

Account structure

A regulated payment account or available-balance structure used for supported pay-ins, FX, payouts and card funding. Virtual account numbers are not separate bank accounts, and this is not a card merchant account or MID.

Account entity, identifiers, currencies, safeguarding and balance rights are contract-specific.

03Merchant settlement

When are sale proceeds settled, and who sends them to the merchant?

Settlement makes processed sale proceeds available to the merchant.

Merchant settlement

Sale proceeds and settlement responsibility

Enabled money movements

May apply

Available only where the selected Nium regulated entity can approve the client and requested account capability. Supported currencies, funding source, use case, due diligence and regulatory permissions apply.

Currency, balance, bank rail, cut-off and destination rules apply.

Pricing & settlement terms

Terms to confirm in the agreement

Price

  1. Which account, identifier, incoming-payment, refund, payout, sweep and balance charges apply?

    Pricing is configuration- and contract-specific.

Payment-account balance & safeguarding

  1. What safeguarding, balance, rail, cut-off, limit and post-termination access rules apply?

    Payment-account funds handling depends on the approved account terms.

Reporting data flow · Multi-currency payment accounts provided by a Nium regulated entity

How are payment data, reports, exports and reconciliation handled?

Payment-account integration, balance events & bank-rail flows

Reporting data flow

Connect data sources → refresh → report → export & reconcile

The reporting setup determines connected data sources, report coverage, update timing, exports and reconciliation keys.

Selected product

Multi-currency payment accounts provided by a Nium regulated entity

Connected payment data, report coverage, refresh timing, exports and reconciliation.

  1. Checkout routes

    No checkout integration is specified for this product

    Not specified
  2. Gateway integration, security and transaction tools

    No payment gateway is specified for this product

    Not specified
  3. Payment-account, balance & rail responsibilities

    Nium provides the regulated payment account and ledger · Named or virtual identifiers route eligible funds to the account

  4. Reporting & reconciliation

    Depends on the product, payment rail, provider response, card-network clearing, beneficiary delivery and configured API or Portal workflow.

01

Checkout routes

Which providers, accounts and data sets are connected?

The actual integration surfaces, UI ownership and deployment choices.

Checkout integration

Not specified

No checkout integration is specified for this product

02

Gateway integration, security and transaction tools

Which reports and transaction fields are available?

API entry points, testing, events, tokens and authentication.

Selected setup

Reports entry point

How requests enter this product and which integration boundary applies.

Payment gateway

Not specified

No payment gateway is specified for this product

Gateway integration, security and transaction tools

Report coverage and available data

Reports

No additional gateway integration, security and transaction tools details are specified.

Recurring operations

Recurring operations

Subscription creation, stored credentials, retries and who controls the schedule.

Recurring billing availability
Not specified

Recurring billing is not specified for this product

03

Payment-account, balance & rail responsibilities

Who supplies transaction data, consolidates reports and performs reconciliation?

The regulated account entity, account ledger, safeguarding bank and enabled bank rails for this configuration.

Payment-account, balance & rail responsibilities

  • Nium provides the regulated payment account and ledger
  • Named or virtual identifiers route eligible funds to the account
  • A connected bank supports the safeguarding structure
  • Refunds, payouts and sweeps use enabled account rails

A regulated payment account or available-balance structure used for supported pay-ins, FX, payouts and card funding. Virtual account numbers are not separate bank accounts, and this is not a card merchant account or MID.

04

Reporting & reconciliation

Which exports, identifiers and reconciliation workflows are available?

What operations teams can reconcile, how quickly data arrives and where exceptions are handled.

Reporting & reconciliation

Provider data → refresh → report → export & reconciliation

Export formats, identifiers, correction handling and reconciliation workflows.

  1. 01

    Reporting & reconciliation

    What operations teams can reconcile, how quickly data arrives and where exceptions are handled.

    Financial report availability

    Availability
    Depends on the product, payment rail, provider response, card-network clearing, beneficiary delivery and configured API or Portal workflow.

    Consolidated reporting

    Included with this product

    Reconciliation

    Product name
    Nium Portal and API reporting
    Automated matching
    Yes
    Multiple data sources
    Yes
    Status discrepancy handling
    Nium transaction and account reporting should be reconciled with the client's funding bank, beneficiary bank, card network, travel supplier or other external rail. A transaction state does not convert a virtual account number into a separate bank account or Nium into the client's merchant acquirer.

Before integration

Integration details not specified

  1. 01

    Which hosted, embedded or direct-API checkout is contracted for Multi-currency payment accounts provided by a Nium regulated entity, and who owns the UI and PCI scope?

    No checkout integration is specified for this product.

Merchant funds, risk & support

Nium Multi Currency Accounts: risk, licenses & support

Payment processing, merchant funds, reserves, chargebacks, contracting entity, regulated payment services and support.

Nium Multi Currency AccountsService: Multi-currency payment accounts provided by a Nium regulated entity
01 / Processing, reserves & chargebacks

Who can suspend payment processing or hold merchant funds?

Payment processing, reserve or other holds on merchant funds, fraud controls and chargeback handling.

Payment processing & funds

Regulated payment account & virtual identifiers

Nium provides the approved payment account, account ledger and linked named or virtual identifiers. The account agreement defines the holder, currencies, safeguarding bank, balance rights and enabled incoming, refund, payout or sweep rails; no card MID or acquiring service is included.

Role in this product
Payment account provider · Payment account technology provider
Who receives and settles funds
Varies by agreement

Reserve or security deposit

Reserve amount and release terms are not specified

The reserve amount and release schedule are not specified for this product. A reserve may still be included in the final agreement.

Not specified
Before signingReserve, chargeback, settlement hold and suspension terms4 items to confirmReview contract terms
03 / Support

How can merchants reach support?

Company support hours and contact channels are available. It is not specified which ones cover Multi-currency payment accounts provided by a Nium regulated entity and payment-processing or merchant-settlement issues. First-response and resolution targets are also not specified.

Support contacts

Company support hours and contacts

The contacts that cover this product and payment-processing or merchant-settlement issues are not specified.

Company contacts

Support hours are not specified for these contacts.

Developer

Before signingSupport contacts, hours and response times3 items to confirmReview contract terms
Multi-currency payment accounts provided by a Nium regulated entity / Before signing

What should the merchant agreement include?

Confirm the contracting entity, approval conditions, processing fees, merchant funding, reserves, chargebacks, liability, support and termination.

Before signing

Multi-currency payment accounts provided by a Nium regulated entity: terms to confirm

Confirm each material commercial, operating and legal term in the agreements that govern this product.

Commercial & funding terms

Processing fees, reserve or security deposit, merchant funding schedule and chargeback fees

Approval, liability & exit

Underwriting conditions, responsible entities, loss allocation, suspension, support and termination

Contract checklist

Terms to review by topic

Jump to the underlying product details

  1. 01Reserves & chargebacksReserve or security deposit, chargebacks, processing suspension and settlement holds.
  2. 02Legal entity & licenseContracting entity, license or registration, and regulated payment services.
  3. 03SupportSupport contacts, hours, response times and escalation.
Merchant agreement

Contract terms to confirm

Review processing fees, merchant funding, reserves, chargebacks, liability, support and termination.

Reserves & chargebacksReserve or security deposit, chargebacks, processing suspension and settlement holds.
  1. Can a reserve or post-termination hold apply to this product, and how is it released?

    The entity that may establish and hold a reserve, the reserve amount and the release terms are not specified.

  2. What events allow Multi-currency payment accounts provided by a Nium regulated entity to be suspended or terminated?

    The notice period, any right to cure a breach, and the events allowing immediate suspension are not specified.

  3. Which contracted provider handles chargeback alerts, representment and card-network monitoring?

    The provider responsible for chargeback alerts, representment and card-network monitoring is not specified.

  4. Who handles open disputes, chargebacks and case submissions after termination?

    Ownership of open disputes, chargebacks and case submissions after termination is not specified.

Legal entity & licenseContracting entity, license or registration, and regulated payment services.
  1. Which legal entity will sign the agreement for this product, and which license or registration applies?

    The contracting legal entity is not specified for this product.

  2. Which privacy framework, controller roles and data-transfer terms apply to this product?

    The privacy framework, controller roles and data-transfer terms are not specified for this product.

SupportSupport contacts, hours, response times and escalation.
  1. What first-response, update and resolution targets apply by incident severity?

    First-response and resolution targets are not specified.

  2. Who handles escalations for payment failures, integration incidents and account restrictions?

    No escalation contact or process is specified for these incidents.

  3. Which support hours and contact channels cover Multi-currency payment accounts provided by a Nium regulated entity, and where should a merchant report payment-processing or merchant-settlement issues?

    The support scope for Multi-currency payment accounts provided by a Nium regulated entity and the contacts for payment-processing or merchant-settlement issues are not specified.

Product summary

What this product already includes

What this product includes, which restrictions apply and which merchant-agreement terms are not specified.

Included capabilities

Capabilities included with Multi-currency payment accounts provided by a Nium regulated entity.

  • Receive approved pay-ins, maintain available balances in supported currencies, convert funds and fund payouts or issued cards through a Nium payment-account structure. A virtual account number is a notional identifier linked to a settlement account and is not a separate bank account. The relevant Nium entity or, in the United States, the program bank controls custody and regulated payment services.