White label / grey label
Deploy accounts, payments, IBANs or compliance journeys in your own environment, with an integration model suited to your project.
In brief
API, grey label and white label describe how far Tractial is embedded and how visible it remains. The partner’s commercial brand does not change the regulated provider or disclosure duties.
White label and grey label offerings allow a platform to embed financial services into its user experience without building the entire technical and regulatory infrastructure in-house. Tractial reviews projects from partners wishing to offer an embedded financial experience, with a clear operational framework and defined responsibilities.
Three integration levels
- API
Services embedded in the partner journey. Tractial stays visible as the provider.
- Grey label
Experience carried by the partner, with Tractial’s role disclosed as required.
- White label
Components inside an experience strongly carried by the partner, subject to the contract and the rules.
Teaching comparison. Mandatory disclosures can apply at every level.
Three integration models
API integration
Tractial’s services are embedded into the partner’s journey via API; Tractial remains visible as the service provider.
Grey label
The experience is carried by the partner, with Tractial’s role disclosed as required by applicable obligations.
White label
Certain components are embedded into an experience fully carried by the partner, subject to the applicable contractual and regulatory framework.
Components available depending on scope
- Payment accounts and IBANs
- Incoming and outgoing payments
- KYC / KYB and compliance
- Reporting
What does not change
Services remain operated by Tractial, unlike agent status. Certain payment-service-provider disclosures may be mandatory.
Integration framework
Services are provided under Tractial’s Payment Institution licence (ACPR), subject to project eligibility, compliance validation, contractual agreement and the applicable regulatory framework.
FAQ
What is the difference between white label and grey label?
White label aims for an experience strongly carried by the partner. Grey label keeps more visibility on the role of the infrastructure or service provider. Terms must be defined project by project.
Can we integrate only certain components?
Yes, the scope can be tailored: accounts, IBANs, payments, compliance or reporting depending on needs and the required validations.
Can the partner completely hide Tractial’s role?
No. Certain disclosures about the payment service provider may be mandatory under the applicable regulatory framework, whichever model is chosen.
How does this differ from the agent status?
Under white label / grey label, services remain operated by Tractial. The payment institution agent status allows the partner to carry out certain activities itself on behalf of Tractial, under a dedicated regulatory framework.
Related pages
PI agent
When the partner itself carries out certain activities.
See the pageAPI
The technical journey.
See the pageFintechs
Choose a launch model.
See the pageAccounts
A component often embedded.
See the page