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

Payment Providers Overview#

Our hosted page offers methods configured for your brand and the shopper's Country. You do not submit the provider or method(s) in the request - instead you must configure the method(s) from your Mozarto back office. Then when creating a session, the system will automatically look up your active configurations for your shopper's Country and show the available methods on the page.

Available methods#

MethodProviderPayment typePage
Debit/Credit CardemerchantpayCard (3D Secure v2)emerchantpay
Google PayWorldpayWalletWorldpay

Adding payment methods#

Payment methods will be shown on the payments page only when all of the following are true:
1.
There is an active Payments module account within the Brand where you want to configure the Payments page.
2.
The Payments module account has the credential the method needs: apiKey for emerchantpay (card) and googlePayGatewayMerchantId for Worldpay (Google Pay). An account without it is skipped, so the next matching account by priority is used instead. See each provider page.
3.
The Processing scope of said Payments module account covers the session's country and currency. When several accounts match, Mozarto uses the one with the highest priority (priority 1 first; this can be defined within your Payments account).
4.
Your brand has an active Payment Page configuration for the session country, and the method is added to that configuration.
If no method is left, session creation fails with 400 PSP Configuration not found. Please check you psp Configuration. If no Payment Page exists for the country, it fails with 400 No active payment page is configured for this brand and country.

Method list or direct form#

Within your Payment Page configuration you can add a single payment method or multiple payment methods. If one method is available for the session, the page opens that method's input form or button directly. If several are available, the page first shows a lobby where your shopper selects a method before entering any required payment details.
The count is based on the methods available after the checks above, not the methods listed on the Payment Page. A method skipped by those checks does not count.

Collected fields#

The page collects the fields each method needs.
MethodAlways collected
Debit/Credit Cardstreet, city, postalCode, plus state for US, CA, and AU
Google PayNone
Modified at 2026-11-02 12:02:21
Previous
Worldpay
Next
Sample requests
Built with