White Label
Launch a financial service for your audience. We'll help build the customer account and operations dashboard under your brand and connect them to payment infrastructure.
Branding demo. Services and card issuing terms depend on the provider's program.
UNDER YOUR BRAND
Customers check balances and make payments. Your team can review accounts, transactions and requests for help.
FOR YOUR CUSTOMERS
Receiving money, paying by card and checking transactions in your branded app.
FOR YOUR TEAM
Customer records, transactions and enquiries in one workspace. Your team reviews payments and handles questions while you manage your service's pricing.
WHITE LABEL SCOPE
We start by defining the customer screens, your team's responsibilities and the operations the provider will handle.
Registration, account details, cards, payment history and document requests, using your service's name, colours and copy.
Manage customers, reviews, payments, enquiries and fees. Assign access according to each person's role.
Connect the agreed functions, process status updates and match transactions. Accounts, payments and cards form part of the agreed scope.
Acceptance scenarios, support instructions and checks of the customer journey. Before launch, we agree who owns each stage.
The difference is how much your team has to build. Customer checks, program approval and payment rules apply to both approaches.
Build in-houseDesign and build your customer app
white.cards White LabelWe adapt the customer app to your brand
Build in-houseBuild tools for support and payment monitoring
white.cards White LabelWe configure the team workspace for your agreed processes
Build in-houseImplement API calls, events and error handling
white.cards White LabelWe connect the selected program and test its payment flows
Build in-houseAgree eligibility and terms with the provider
white.cards White LabelWe include the provider's requirements in the project scope
Your brief determines scope, timing and cost. White Label doesn't replace licensing, banking services or customer approval.
Define your projectSERVICE ECONOMICS
Set your payment volume, fees and costs to see what's left each month. Every assumption is editable.
Remaining after listed costs
$1,
per month
Any costs you haven't included still need to be paid from this amount
These figures are examples, not white.cards or provider prices. Calculation: volume × your fee + subscription revenue − provider costs − fixed costs. Taxes, refunds, exchange-rate differences and other unlisted costs are excluded.
Choose API integration if you already have a customer app. Your team can add card functions to the existing interface.
THE LAUNCH PLAN
Agree on the program, build the integration, run a pilot and prepare to onboard more customers. Each stage has a result to check before moving on.
Step 01
Define the customers, their countries and the payments they need. Agree service eligibility, checks and terms with the provider.
Result: agreed launch terms
Step 02
Brand the customer account and connect payment functions and the operations dashboard. Test the product with sample data.
Result: a product ready for the pilot
Step 03
A small customer group completes onboarding and makes its first payments. Review failures and support requests.
Result: evidence from real transactions
Step 04
Fix the issues found in the pilot and review servicing costs before preparing to onboard the next customer group.
Result: a plan for further onboarding
PRODUCT QUESTIONS
White Label or API, integration timing and card program terms.
All questions and answersWe're preparing the first launch. Development, provider program approval and a pilot come before customer onboarding. The site currently offers interface demos and details of the White Label and API models.