LogoLogo
NymCardAPI catalogContact usnFront catalog
  • NYMCARD DOCUMENTATION
  • Get Started
    • nCore API Quick Tutorial
    • API Core Principles
    • Program management
      • Manage documents by APIs
      • User KYB process
      • Necessary parameters per user type
      • User ID verification by SDK
      • User KYC process
    • Issuance
      • Users
      • Cards
    • Issuing Physical Cards
      • Individual card issuance
      • Bulk card issuance
      • Card fulfillment
      • Card PIN management
      • Card replacement
      • Proxy number usage
    • Issuing Virtual Cards
      • Migration of virtual to physical card
    • Funding and transfers
      • Funding
      • Internal funding source
      • External funding source
        • From card
        • From bank account
        • Lean API flow
        • DAPI direct API flow
      • Transfers
      • Western Union APIs
    • Product Management
      • Card product
      • Balance limits
      • Velocity limits
      • Fees
      • Charges
      • Multi-currency
      • Authorization controls
        • Enhancements for MCC list management
    • Transactions
      • Payment ecosystem
      • Transaction lifecycle
      • Transaction types
      • Transaction endpoints scenarios
      • Multi-clearing process
    • Webhooks
      • Introduction to webhooks
      • nCore webhook events
      • Steps to configure a webhook
      • Webhooks samples
      • Webhook changes for simulation
      • Webhooks management
    • Security
      • PCI widget
      • 3D Secure
      • OTP SMS templates
    • Release announcements
      • Embedded Lending Release Notes
      • Changes in the release on 13/07/2023
      • Changes in the release on 23/05/2023
      • Changes in the release on 04/04/2023
  • For developers
    • nCore API catalog
    • nFront API catalog
Powered by GitBook
On this page

Was this helpful?

  1. Get Started
  2. Issuing Physical Cards

Card fulfillment

Card fulfillment mechanism helps you to track your newly created physical cards request. Fulfillment mechanism is managed for two possible cases:

  • Individual card fulfillment

  • Bulk cards fulfillment

Individual card fulfillment

This card fulfillment is appropriate for a single cardholder. Cardholders receive their personalized cards by mail at the addresses provided in the create card request.

Bulk cards fulfillment

This card fulfillment enables you to create N number of non-personalized cards in bulk form. The bulk of cards is delivered to the shipping address provided in the create bulk card issuance request. Bulk cards fulfillment is a good option when you want to have more control over individual card details e.g., assigning specific user tokens.

Card fulfillment status

When a card is fulfilled, the fulfillment_status field of the card object and the bulk issuance object is updated. For physical cards, fulfillment providers (perso vendors) offer different shipping options. If the fulfillment provider supports live tracking and status updates then the fulfillment_status will be updated and will reflect the live status of card fulfillment journey.

Fullfullment status

Description

Created

On card creation, the fulfillment status is set as created

Ordered

When embossing request for the card is generated, the status is updated as ordered

PreviousBulk card issuanceNextCard PIN management

Last updated 9 months ago

Was this helpful?