1. Payment Providers (PSPs)
Mozarto - The Payments Orchestration Platform
  • 1. Introduction
  • 2. Authentication
  • 3. Redirect API
    • Pay-In Flow
    • Pay-Out Flow
    • Webhook Setup
    • Country Codes
    • Errors
    • Payment Providers (PSPs)
      • Overview
      • Brite
      • CashLib
      • Cleo
      • Contiant
      • emerchantpay
      • Flexepin
      • ForumPay
      • Gigadat
      • Neosurf
      • OFApay
      • PawaPay
      • PayModum
      • PayOne
      • Trust Payments
      • Worldpay
    • Sample requests
      • Overview
      • Pay-In
        • Brite
        • CashLib
        • Cleo
        • Contiant
        • emerchantpay
        • Flexepin
        • Forumpay
        • Gigadat
        • Neosurf
        • OFApay
        • PawaPay
        • Paymodum
        • PayOne
        • Trust Payments
        • WorldPay
      • Pay-Out
        • Cleo
        • Forumpay
        • Gigadat withdraw ACH
        • Gigadat withdraw ETO
        • OFApay
        • PawaPay
        • PayOne
        • Trust Payments
      • Webhook
        • PayOne status webhook
        • ForumPay status webhook
  • 4. Hosted page API
    • Pay-In Flow
    • Webhook Setup
    • Country Codes
    • Errors
    • Payment Providers (PSPs)
      • emerchantpay
      • Worldpay
      • Overview
    • Sample requests
      • Overview
  • Schemas
    • TransactionData
  1. Payment Providers (PSPs)

Overview

PSP Overview#

Supported operations#

ProviderPay-InPay-OutWebhookPayment type
ForumPay✓✓✓Cryptocurrency
Gigadat✓✓✓Bank transfer
Worldpay✓-✓Card
Trust Payments✓--Card
Cleo✓✓✓Bank transfer
PayOne✓✓✓Bank transfer
Neosurf✓-✓Voucher
Flexepin✓--Voucher
Brite✓-✓Bank transfer
emerchantpay✓-✓Card
Contiant✓-✓Bank transfer
PawaPay✓✓✓Mobile Money
CashLib✓-✓Voucher
OFApay✓✓✓E-wallet / QR / Bank transfer
Paymodum✓✓✓Bank transfer (US ACH)

Endpoint#

All transactions use the same endpoint. Set pspType to select the provider:
POST /v1/api/mozarto/cashier
Body fieldDescription
pspTypeProvider code - see values in the table below
type"PAYIN" for Pay-In, "PAYOUT" for Pay-Out
countryCountry of the payer - required on every request (see Country)

pspType values#

ProviderpspType
ForumPay"FORUMPAY"
Gigadat"GIGADAT"
Worldpay"WORLDPAY_EU"
Trust Payments"TRUST"
Cleo"CLEO"
PayOne"PAYONE"
Neosurf"NEOSURF"
Flexepin"FLEXEPIN"
Brite"BRITE"
emerchantpay"EMERCHANTPAY"
Contiant"CONTIANT"
PawaPay"PAWAPAY"
CashLib"CASHLIB"
OFApay"OFAPAY"
PayModum"PAYMODUM"

Pay-In request fields - at a glance#

FieldForumPayGigadatWorldpayTrustCleoPayOneNeosurfFlexepinemerchantpayContiantBritePawaPayCashLibOFApayPayModum
baseamount✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓
currency✓optional✓✓✓✓✓✓✓✓✓✓✓✓✓
email✓✓✓✓✓✓✓✓✓optionaloptional--from token✓
country✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓
firstName / lastName-optional✓✓✓✓--✓optionaloptional--from token✓
phone-✓✓✓✓✓--optional--optional✓✓optional
Card details--✓✓----✓------
voucherPin-------✓-------
dob--✓✓✓-----optional-✓-optional
Full address-optional✓✓✓---optional-optional-✓optionaloptional
paymentMethod-------------✓-
ssn--------------optional
For the full field list for each provider, click through to the individual PSP page.

Country#

Send country on every Pay-In and Pay-Out request, for every provider. Mozarto matches it against the Processing Scope configured for the provider - first at company level, then on the account your brand uses (Payments Module - your brand - the account - Processing Scope). A request whose country falls outside either scope is rejected with HTTP 400.

Accepted values#

For scope matching, Mozarto accepts any of three forms, case-insensitively, and normalizes them internally:
FormExample
Full country name"Germany"
ISO 3166-1 alpha-2"DE"
ISO 3166-1 alpha-3"DEU"
The full list of accepted names and codes is on Country codes.
Mozarto converts the value to the format each provider needs, so the same three forms work for every provider. Some providers serve only certain countries (for example, Cleo serves only Chile, Peru, and Mexico), and several derive the charged currency from the country - see the provider page.

If you omit it#

Mozarto resolves the country by geo-locating the caller's IP address and continues with the country it detects. Treat that as a safety net, not a feature:
Server-to-server calls, proxies, VPNs, and load balancers report the country of your infrastructure, not the payer's. A wrong country routes the transaction to the wrong account or rejects it.
When the IP cannot be resolved to a country, the scope check is skipped entirely, so a request that should have been rejected may go through to the provider.
Providers that need the country in their own payload still fail without a usable value.
Always send country explicitly.
Modified at 2026-11-02 13:15:49
Previous
Errors
Next
Brite
Built with