--- title: "Introduction" slug: "introduction-1" updated: 2026-05-13T12:09:00Z published: 2026-05-28T15:06:20Z canonical: "www.documentation.paynetics.digital/introduction-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://www.documentation.paynetics.digital/llms.txt > Use this file to discover all available pages before exploring further. # Introduction ### Discover our products and how you can deliver them to your customers Paynetics provides a modular payment infrastructure that enables you to build, launch, and scale financial products across Europe and the UK. Whether you are issuing cards, managing payment accounts, enabling transfers, or acquiring payments, our products are designed to be combined and delivered through multiple channels depending on your business model. This section gives you a high-level overview of our core products and the delivery channels available to bring them to market. ### Products | #### Cards Issuing Issue **physical and virtual Visa and Mastercard cards** under your own brand. Card issuing capabilities include: - Virtual and physical debit cards for consumers and businesses - Custom card design and branding - Card controls, limits, and fee configuration - Support for **Apple Pay and Google Pay** - Tokenization and secure card data handling Cards can be linked to payment accounts or virtual accounts and configured to support a wide range of use cases, from everyday spending to controlled business expenses. | #### Payment Accounts Open and manage **payment accounts and e-money wallets** for your customers. Payment Account capabilities include: - **Dedicated IBANs** (where applicable) - Multi-Balance account structures - Virtual accounts for advanced fund and card setups - Support for consumer and business accounts Payment accounts act as the foundation for card usage, transfers, and settlement flows. | | --- | --- | | #### Transfers Enable **domestic and international money movement** across supported schemes. Transfer capabilities include: - SEPA Credit Transfers - Faster Payments (UK) - Real-time internal transfers between Paynetics accounts - Funding and payout flows for cards and merchants Transfers can be initiated via API and integrated into your product flows for top-ups, payouts, and peer-to-peer use cases. | #### Acquiring Accept card payments and enable merchant acquiring services. Acquiring capabilities include: - Merchant onboarding and configuration - Card payment processing - Settlement and reconciliation - Support for additional services such as OCT and AFT, subject to approval Acquiring can be combined with issuing and payment accounts to support closed-loop or full-stack payment solutions. | ### How the Products Fit Together Paynetics products are designed to work together as building blocks. A typical setup may include: - **Payment accounts** as the foundation for holding and moving funds - **Cards issuing** to enable spending from those accounts - **Transfers** to support top-ups, payouts, and inter-account movement - **Acquiring** to accept card payments and settle funds to merchant accounts Partners can start with a single product and expand over time as their use cases evolve. ### Typical Use Cases Paynetics’ platform supports a broad range of use cases, including: - **Digital wallets and neobanks** Offer accounts, cards, transfers, and wallet payments under your own brand. - **Embedded finance platforms** Embed cards, payouts, and accounts into non-financial products. - **Marketplaces and platforms** Onboard merchants, accept payments, and settle funds programmatically. - **Payout and disbursement solutions** Send funds to cards or accounts using transfers and OCT. - **Expense management and business cards** Issue controlled cards linked to accounts with configurable limits and usage rules. ### Delivery Channels How you deliver Paynetics products to your customers depends on your technical setup, speed-to-market requirements, and desired level of control. Paynetics supports multiple delivery channels, which can be used independently or combined. | #### API Integrate Paynetics directly into your product using our APIs and SDKs. API-based delivery enables you to: - Fully embed payments, accounts, cards, and transfers into your product - Design custom user journeys and interfaces - Automate onboarding, configuration, and operations - Test and validate your solution using a dedicated sandbox environment This approach provides maximum flexibility and is suited for partners building bespoke financial products. | #### White Label App Launch your own **branded digital banking application** without building the technology from scratch. The White Label App allows you to: - Go live in as little as **two months** - Offer cards, accounts, and payments through a ready-made mobile app - Apply your branding and product configuration - Avoid client-side development and maintenance This option is ideal for partners who want a fast time to market with minimal engineering effort. | #### BIN Sponsorship Issue cards under a **BIN sponsorship model**, and directly manage the issuing processor relationship. BIN sponsorship enables you to: - Issue payment cards using your own dedicated BIN - Full control over the Issuing processor relationship - Issue cards like a scheme member without needing to be one This model is commonly used by partners who are either licensed institutions without scheme membership or fintechs who want to have full control over the issuing experience with direct processor relationship. | | --- | --- | --- | ### Getting Started To get started with Paynetics: 1. Understand the Key Concepts 2. Discover the Delivery Channels and Products 3. Design your fintech solution The rest of this documentation portal provides detailed guidance, API references, and implementation examples for each product and delivery channel. An **Account** is a payment or e-money account used to hold funds and execute transactions. Accounts are created under a specific instance and program and are associated with either a user or a merchant. They provide the logical structure under which balances, cards, and transactions are organised. Common account purposes include: - executing card payments and transfers - holding settlement funds - pre-funding services such as OCT An account acts as a container for balances rather than holding funds directly. A **Balance** represents an amount of funds held in a specific currency within an account. An account may have multiple balances, typically one per supported currency. Balances are assigned payment identifiers such as IBANs or account numbers, depending on the currency. All monetary operations reference a **balance token**, which is used in API calls to debit or credit funds, perform transfers, or apply fees.