How to Launch a White-Label Payment Card Programme: The Complete 2026 Infrastructure Guide

The guide is about the infrastructure and operational steps required to launch a white-label payment card programme using Wallester. It details the commercial agreements, compliance checks, technical API integration, and go-live procedures for non-financial and financial institutions.

Launching a custom card programme with Wallester requires four distinct operational phases. This infrastructure allows non-financial companies, fintech startups, and financial institutions to issue Visa cards without acquiring their own principal membership.

The launch roadmap includes:

1. Commercial kick-off: Formalising the partnership through a Letter of Intent (LOI) and selecting the appropriate subscription tier.
2. Due diligence & scoping: Completing Know Your Business (KYB) checks, defining card types (credit, debit, or prepaid), and finalising the Master Agreement.
3. Technical implementation: Executing API integration, obtaining Visa Co-brand approval, configuring the dedicated BIN range, and setting up 3D Secure protocols.
4. Go-live & operations: Activating the programme for public issuance, managing settlements, and enabling tokenisation for Apple Pay and Google Pay.

What is Embedded Finance, and why use a BIN sponsor?

Modern platforms often need to integrate financial services directly into their user interface, a practice known as Embedded Finance. For many businesses, from neobanks to gig economy platforms, becoming a direct Visa Principal Member is cost-prohibitive and time-consuming.

Wallester resolves this by acting as the BIN Sponsor and issuer. This setup allows you to issue physical and virtual Visa cards under your own brand while Wallester handles the regulatory heavy lifting, including settlement, licensing, and scheme compliance.

Further Reading: How to Build an Embedded Card Program

Defining the programme structure

Before technical integration, you must select the card architecture that fits your business model.

1. Card types: risk vs. revenue

2. Form factors: physical vs. virtual

The 4-phase launch protocol

Phase 1: Commercial kick-off

The process begins with the Letter of Intent (LOI). This document outlines the commercial terms and signals your commitment to the project. Upon signing, you enter the subscription model, which covers the maintenance of the card programme. This stage confirms your intent to proceed and reserves the necessary resources for your project.

Phase 2: Compliance & due diligence

Wallester operates as a regulated Electronic Money Institution (EMI). Therefore, strict compliance is mandatory before any technical work begins.

• KYB checks: You must submit corporate documents for “Know Your Business” verification to confirm legal standing and ownership structure.
• Scope definition: You define the specific parameters of your programme, such as currencies (EUR, USD, GBP, etc.), card expiry dates, and spending limits.
• Master agreement: Once due diligence is cleared, both parties sign the final Master Agreement, which governs the long-term partnership.

Phase 3: Technical implementation

This is the build phase where your product connects with the Visa network via Wallester’s infrastructure.

• Visa co-brand approval: Your card design (plastic or digital art) is submitted to Visa for brand compliance verification.
• BIN setup: A dedicated Bank Identification Number (BIN) range is assigned to your programme. This unique identifier routes transactions specifically to your platform.
• API integration: Your development team connects to the Wallester REST API to enable features like card creation, pin setting, and balance checks.
• Security configuration: You configure 3D Secure (3DS) for online fraud protection and set up PCI DSS-compliant data handling procedures.

Phase 4: Operations & go-live

With testing complete, the programme moves to production.

• Live issuance: You begin issuing real cards to your customers or employees.
• Settlement: Wallester manages the daily settlement of funds with Visa, reconciling transactions against your funding account.
• Support: A dedicated Client Relationship Manager is assigned to assist with operational queries, disputes, and scaling requirements.

Further Reading: Building a Unified Financial Architecture with Wallester API and ERP Tools

Post-launch operations: tokenisation

Modern users expect mobile wallet compatibility. Wallester supports “Push Provisioning,” allowing users to add their cards directly to digital wallets from your app.

Supported wallets:

• Apple Pay
• Google Pay
• Samsung Pay
• Garmin Pay
• Fitbit Pay
• Fidesmo Pay

This capability is essential for increasing transaction volume, as it allows virtual cards to be used at physical Point of Sale (POS) terminals via NFC.

Investment & pricing models

Wallester operates on a subscription-based model for our White-Label solution. As every financial product is unique, these contracts are customised based on your projected transaction volume and risk profile.

To help you structure your project’s financial planning, the indicative starting subscription tiers for card programme maintenance are as follows:

Note: Final pricing is confirmed after the Due Diligence phase. The model prioritises a “pay-as-you-go” approach with no hidden setup fees.