# Introduction

**Welcome to the Zūm Rails Card Issuance Documentation.**

Zūm Rails enables Canadian partners to deploy, manage, and scale both Prepaid and Secured Credit Card programs. Our platform bridges the gap between traditional banking rails and modern fintech needs, offering real-time card issuance, automated KYC/IDV workflows, and integrated funding via Canada’s most popular payment methods. With Zūm Rails' white-label solutions and APIs, you can issue virtual and physical cards, configure card details, manage funding, and handle cardholder information with ease

### Key Features

* **Unified BaaS Architecture:** A single integration point for full Card Program Management, including regulatory oversight, fraud monitoring (AML/CTF), and chargeback management.
* **Integrated Identity Verification (Zūm KYC):** Fully automated, white-label onboarding powered by AiPrise. We handle the "Exact Match" logic for legal names and DOBs against ID documents to ensure compliance and high pass rates.
* **Security & Tokenization:** As a PCI Level 1 provider, we utilize advanced tokenization. Our SDKs ensure sensitive card data (PAN, CVV) never touches your servers, drastically reducing your compliance burden, so you don't have to.
* **Plug & Play Customizable Brand Experience:** Tailor everything from the virtual and physical card design to the web-based cardholder interface. Use our Zum Connect SDK to embed these features or redirect users to a Zūm-hosted, white-labeled environment. Alternatively, access all this information via API and build it into your own frontend experience. Zūm handles the full card program management — including program setup, card velocity limits, fraud monitoring, compliance, cardholder agreements, digital and plastic card issuance, and chargeback oversight.
* **Fully Compliant:** Zūm Rails is Level 1 PCI compliant, so you don’t have to be. Our SDKs tokenize card numbers to keep your cardholders’ data secure.
* **Tailored to Your Business:** Customize the card design, platform, and cardholder interface to match your brand.
* **Monetization Engine:** Our programs are built to generate interchange and fee revenue, turning your card product into a profit centre from day one. Ask our sales team for a demo of the Zūm Card Issuance platform and learn how you can start earning from your card programs.

Zūm Rails offers two flexible integration paths to suit your technical resources and desired speed-to-market:

* **Zūm Rails White-Label Solution**
* **Zūm Rails API Solution**

### Zūm Rails White-Label Solution

This "Plug & Play" approach provides a complete, turn-key cardholder experience with minimal development.

* **Administrative Portal:** Comprehensive tools for your team to manage users, monitor transactions, and handle program-level settings.
* **Hosted Onboarding:** A secure, mobile-optimized web form that handles data collection, OTP verification, and identity documentation.
* **Cardholder Self-Service:** A ready-made portal where users can view balances, check transactions, and manage security deposits.
* **Integrated Payment Gateway:** Native access to the Zūm Rails rails for instant card loading/unloading via Interac e-Transfer, EFT, and Visa Debit.

Zūm Rails provides the card onboarding application in a web form that handles the collection of card profile information and identity verification information from the card applicant.

You can use our hosted [Card Onboarding](/tokenization-1/zum-connect.md#card-onboarding) URL or integrate the process into your application’s embedded flow using our SDK. See [Zum Connect](https://docs.zumrails.com/tokenization-1/zum-connect) and [Card Onboarding](/tokenization-1/zum-connect.md#card-onboarding) for integration details.

List of SDKs

* [Card Onboarding](/tokenization-1/zum-connect.md#card-onboarding): Handles the end-to-end applicant journey from profile setup to KYC.
* [View Card Information](/tokenization-1/zum-connect.md#view-card-information): Securely renders sensitive card details (PAN/CVC) within your UI.
* [Card Funding Checkout](/tokenization-1/zum-connect.md#card-funding-checkout): A modular UI component for managing security deposits and card loads.

### Zūm Rails API-first Solution

Designed for partners building bespoke financial experiences, our APIs offer deep programmatic control over the entire card lifecycle.

* **Programmatic Issuance:** Trigger card creation and activation instantly upon KYC approval.
* **Lifecycle Control:** Manage card states (Active, Blocked, Closed, Reissue) via backend triggers.
* **Real-Time Data Streams:** Access granular transaction history, balance inquiries, and cardholder metadata to power your own analytics or user dashboards.

Zūm Rails [Cards API](/api-reference/cards.md) solution allows you to instantly issue cards, access card account information and transaction data to effectively manage your card program and card lifecycle management.

List of API's

* [Approve Card](/api-reference/users.md#approve-a-card)
* [Activate Card](/api-reference/cards.md#activate-card)
* [Update Card Profile](/api-reference/users.md#update-a-card-information)
* [Update Card Program](/api-reference/cards.md#update-card-program)
* [Get Balance Inquiry](/api-reference/cards.md#get-balance-inquiry)
* [Update Card Status](/api-reference/cards.md#update-card-status)
* [Reissue Card](/api-reference/cards.md#reissue-card)
* [Get Card Transactions](/api-reference/cards.md#get-card-transactions)
* [Load and Unload Card](/api-reference/transactions.md#creating-a-new-transaction)

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zumrails.com/tokenization/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.