Overview

CardInfra FIP Prepaid is a Card-as-a-Service (CaaS) infrastructure that enables banks and fintech partners to collaborate on the issuance and management of prepaid cards.

The solution is designed for partners that want to build card-based products without independently operating the underlying prepaid card infrastructure.

How it works

┌──────────────────────┐
│    FINTECH PARTNER   │
│                      │
│ Customer Application │
│ Product / Platform   │
└──────────┬───────────┘
           │ API
           ▼
┌──────────────────────┐
│   CardInfra FIP      │
│      Prepaid         │
├──────────────────────┤
│ Customer Management  │
│ Card Management      │
│ Funding              │
│ Card Requests        │
│ Transaction Access   │
└──────────┬───────────┘
           │
           ▼
┌──────────────────────┐
│    PROVIDUS BANK     │
│                      │
│ Prepaid CMS / Ledger │
│ Card Authorization   │
└──────────────────────┘

When a partner loads a card, the partner's account position with the bank is debited and the prepaid card is credited. An unload operation reverses the funding direction.

Sandbox

Use the following base URL for test-bed integration:

Authentication

Partners authenticate using their assigned clientId and clientSecret.

{
  "clientId": "YOUR_CLIENT_ID",
  "clientSecret": "YOUR_CLIENT_SECRET"
}

{
  "successful": true,
  "token": "YOUR_ACCESS_TOKEN",
  "expiration": "2026-10-01T12:00:00Z"
}

Quick start

1. Obtain your sandbox clientId and clientSecret.
2. Authenticate and obtain an access token.
3. Onboard or identify your customer.
4. Retrieve the available card profile.
5. Request the card.
6. Associate the card with the customer where applicable.
7. Load the card with funds.
8. Retrieve card details and balance as required.
9. Use card transaction APIs or the agreed notification mechanism to keep your platform informed.

Customer onboarding

{
  "firstName": "John",
  "middleName": "Michael",
  "lastName": "Doe",
  "email": "john.doe@example.com",
  "phone": "08012345678",
  "nationality": "Nigerian",
  "countryCode": "NG",
  "address": "12 Example Street",
  "residentCountry": "NG"
}

{
  "customerId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "existingCustomer": false
}

Profiles

[
  {
    "name": "Example Profile",
    "id": "profile-id"
  }
]

[
  {
    "name": "Prepaid Card",
    "id": "card-profile-id"
  }
]

Card request

{
  "profileId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "cardProfileId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "nameOnCards": ["JOHN DOE"],
  "instantQty": 1
}

{
  "successful": true,
  "requestNo": "REQ-000001",
  "requestId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Card association

{
  "customerId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "cardId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

{
  "successful": true
}

Retrieve cards

GET /api/v1/cards?CustomerId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

{
  "total": 1,
  "data": [
    {
      "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      "maskedPan": "5399********1234",
      "nameOnCard": "JOHN DOE",
      "expiryDate": "12/29",
      "balance": 50000.00
    }
  ]
}

Funding

Funding APIs move value between the partner's account position with the bank and the prepaid card.

{
  "amount": 50000.00,
  "cardId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

{
  "successful": true,
  "requestNo": "REQ-000001",
  "code": "00",
  "message": "Successful"
}

{
  "amount": 10000.00,
  "cardId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

{
  "successful": true,
  "requestNo": "REQ-000002",
  "code": "00",
  "message": "Successful"
}

Card management

{"cardId":"CARD_ID"}

{"cardId":"CARD_ID"}

{"cardId":"CARD_ID","pin":"1234"}

Card transactions

GET /api/v1/card-transactions?CardId=CARD_ID&FromDate=2026-09-01&ToDate=2026-09-30&Page=1&PageSize=20

{
  "total": 1,
  "data": [
    {
      "transactionDate": "2026-09-30T12:30:00Z",
      "maskedPan": "5399********1234",
      "cardholder": "JOHN DOE",
      "amount": "5000.00",
      "currency": "NGN",
      "impactType": "DEBIT",
      "tranType": "PURCHASE",
      "status": 1,
      "terminalId": "TERM001",
      "merchantNameLoc": "Example Merchant",
      "merchantId": "MERCHANT001",
      "rrn": "123456789012"
    }
  ]
}

Funding transactions

GET /api/v1/fund-transactions?CardId=CARD_ID&FromDate=2026-09-01&ToDate=2026-09-30&Page=1&PageSize=20

{
  "total": 1,
  "data": [
    {
      "transactionDate": "2026-09-30T12:00:00Z",
      "maskedPan": "5399********1234",
      "cardholder": "JOHN DOE",
      "amount": "50000.00",
      "currency": "NGN",
      "impactType": "CREDIT",
      "tranType": 1
    }
  ]
}

Transaction notifications

Partners may implement a webhook to receive transaction notifications. This allows the partner platform to update its own customer experience without repeatedly polling for every transaction.

Partners can also retrieve transactions through the card transaction API.

Error handling

{
  "type": null,
  "title": "Validation Error",
  "status": 400,
  "detail": "One or more validation errors occurred.",
  "instance": null,
  "errors": {
    "fieldName": [
      "Validation message"
    ]
  }
}

Security

• Keep clientId and clientSecret confidential.
• Do not commit credentials to source code repositories.
• Protect authentication tokens.
• Do not log card PINs or authentication credentials.
• Use HTTPS for API communication.
• Mask PAN values in logs and support tooling.
• Restrict access to production credentials.
• Use appropriate timeout and retry handling.

Sandbox testing

Before production onboarding, partners should test authentication, customer onboarding, card requests, card lookup, card management, funding, transaction retrieval and relevant failure scenarios.

Support

For sandbox credentials, integration questions and technical support:

When contacting support, include your partner name, environment, endpoint, request timestamp, request reference where available, HTTP status code and response body. Never include client secrets, PINs or other sensitive credentials.