1. 7. Payment Providers (PSPs)
Mozarto - The Payments Orchestration Platform
  • 1. Introduction
  • 2. Quick Start
  • 3. Authentication
  • 4. Webhook Setup
  • 5. Errors
  • 6. Redirect flow
    • Pay-In Flow
    • Pay-Out Flow
  • 7. Payment Providers (PSPs)
    • Overview
    • Brite
    • Cleo
    • Flexepin
    • ForumPay
    • Gigadat
    • Neosurf
    • PayOne
    • Trust Payments
    • Worldpay
    • Emerchantpay
  • 8. Redirect Flow APIs
    • Redirect Flow APIs - overview
    • Pay-In
      • WorldPay
      • Forumpay
      • Payone
      • Gigadat
      • Flexepin
      • Trust
    • Pay-Out
      • Forumpay
      • Payone
      • Gigadat withdraw ETO
      • Gigadat withdraw ACH
    • Webhook
      • Payone status webhook
  • Schemas
    • TransactionData
  1. 7. Payment Providers (PSPs)

Brite

Open banking payment provider using instant bank payments. No card or voucher required - users authenticate directly with their bank.
Operations: Pay-In ✓ | Pay-Out - | Webhook -
Processing: Asynchronous - redirect user to Brite's hosted page
Payment type: Open banking / instant bank transfer
Fields marked with * are required.

Configuration (Mozarto back office)#

FieldDescription
public_key *Brite public key
secret *Brite secret key

Pay-In#

POST /v1/api/mozarto/cashier

Request body#

FieldTypeDescription
pspType *stringAlways "BRITE"
type *stringAlways "PAYIN"
userId *stringYour internal user/player identifier
brandIdstringBrand identifier
Contact your Mozarto account manager for the full list of request body fields required by your Brite account configuration.

Response#

{
  "status": "success",
  "isSuccess": true,
  "data": {
    "status": "PENDING",
    "url": "https://checkout.brite.com/...",
    "sessionId": "60a74038-5b94-427e-8cff-abc123"
  }
}
Redirect the user to data.url. They authenticate with their bank on Brite's hosted page.

Error codes#

Brite transport failures are mapped to normalized Mozarto errorCode values. Use errorCode for programmatic handling.
Mozarto errorCodePSP raw signalWhen
INVALID_PSP_CREDENTIALSHTTP 404 / 401 / 403Brite API key or merchant credentials are missing or rejected
PSP_TIMEOUTHTTP 408 or response body contains "timeout"Brite did not respond in time - safe to retry
PSP_UNAVAILABLEHTTP 5xxBrite service error - safe to retry with backoff
PSP_RATE_LIMITEDHTTP 429Too many requests - retry after a delay
UNKNOWN_PSP_ERRORAny other responseDeposit session creation failed - check data for the raw Brite response
Note: Brite business-level rejections (session creation failures where Brite returns a 200 with an error body) also produce UNKNOWN_PSP_ERROR since the HTTP status is not available at that boundary.
For the full list of errorCode values and retryability guidance, see Errors.
Modified at 2026-06-09 11:01:55
Previous
Overview
Next
Cleo
Built with