A white label payment gateway lets a business offer a payment interface under its own brand using another provider's technology. Branding is part of the arrangement, but the service agreement determines the functions and responsibilities included. European Banking Authority report on white labelling.
Before choosing one, map the service you want to operate. Identify who supplies the technology, who contracts with merchants, who handles payment processing and who resolves operational problems. Use the answers to judge the proposal alongside its appearance and features.
What does white labelling change?
Separate the branded interface from the organisation providing the underlying service. The European Banking Authority distinguishes the brand-facing partner from the financial institution behind its white-labelled services. That financial-services model is useful context, while the proposed gateway contract must establish which functions your arrangement actually includes. White-labelling roles.
Start by writing one sentence describing the service you intend to sell. For example, “A branded payment interface for merchants in an agreed market.” Then list the functions that sentence leaves unresolved. Does the proposed package include the merchant application process, payment processing, settlement reporting and customer support? Ask the supplier to mark each function as included, optional or supplied elsewhere.
A clear list is more useful than assuming every function sits behind a single product name. The payment process guide can help you identify the events and records that need an owner.
Who handles each part of the payment service?
Use the following worksheet during a supplier discussion. The rows are questions to resolve in the proposed arrangement, not a universal allocation of legal duties.
| Area | Question to resolve | Evidence to request |
|---|---|---|
| Branding and software | Which screens, domains and messages can be customised? | A demonstration of the agreed configuration |
| Merchant relationship | Which entity contracts with and approves each merchant? | The proposed contracts and onboarding process |
| Processing and payout | Which parties process transactions and issue payout records? | A documented flow and sample reports |
| Security | Which systems handle cardholder data and how is scope assessed? | Relevant compliance evidence and a responsibility matrix |
| Support | Who owns an unresolved payment or outage? | Escalation contacts and agreed service commitments |
| Exit | What happens to records and integrations when the arrangement ends? | Contractual export and transition terms |
For card acceptance, consult the payment security standards body's merchant guidance and establish the assessment that applies to your implementation. Read the PCI merchant resources. Have the relevant provider or adviser confirm your responsibilities for the actual design.
Keep a named owner and a written reference for every unresolved row. A sales demonstration can establish what the interface looks like. The contract and supporting documentation need to establish what the supplier is committing to provide.
How should you test a proposed gateway?
Consider an illustrative evaluation involving a fictional merchant. The merchant takes an order, refunds part of it and later asks why its payout differs from the original order amount.
Ask the supplier to demonstrate that complete scenario in its test environment. Can you connect the order to the payment, refund and payout records? Which team answers the merchant's question, and which report supports the answer? Record any step that relies on another provider or manual action.
Then repeat the discussion for a failed payment and an interruption to the service. Ask how the proposed integration communicates the outcome and how support establishes the current state. These are acceptance-test questions to agree with the supplier, rather than claims that all gateways implement identical statuses.
Include the exit case in the evaluation. Request a sample of the records available for export and ask what can be retained when the agreement ends. Put important requirements into the proposed terms, with appropriate advice for the market and service involved.
Where Cessor fits
Cessor does not offer a white label payment gateway. If your requirement is crypto payment processing within an existing product, discuss that specific journey with Cessor and confirm the current integration scope. Keep the requirements for a branded gateway separate when evaluating whether the proposed Cessor service fits.
Bring a deposit-to-withdrawal example, the assets and networks you need, and the records your finance and support teams expect. Ask for a demonstration covering the agreed flow and its exception handling. The crypto payment processing guide provides background for that conversation.
Talk to Cessor with the payment journey and operational requirements you want to evaluate.
General information only, not legal, financial or other professional advice. Information and service availability may change. Confirm current features and supported assets with Cessor before relying on this guide. Your applicable service agreement governs the services provided.