Skip to main content

Manual Provisioning

This page covers everything you need to enable manual provisioning, where end customers add their card by opening Apple Wallet or Google Wallet and scanning or typing in the card number. By the end, your Bank Identification Number (BIN) is tokenized, and every card on it can be added to either wallet. Tokenization is also the prerequisite for push provisioning, so complete this page first. To get there, you send Unit your program and legal details, such as your card art and cardholder terms. Unit submits them to Visa, which approves your brand assets and tokenizes your BIN.

Manual provisioning in four steps: you send program details, Apple reviews your program for Apple Wallet, Visa tokenizes your BIN, and end customers can add cards in the wallet app

How Tokenization Is Set Up​

Visa sets up tokenization for your program. Most programs are tokenized for Apple Wallet and Google Wallet at the same time across the entire BIN, so once tokenization is live, every card on that BIN can be added to either wallet manually.

The two wallets get there differently:

  • Google Wallet: Visa handles tokenization directly. Nothing is required from you beyond the program and legal information below.
  • Apple Wallet: Apple also reviews your card program before Visa can complete tokenization. See Apple's Program Review.
StepTypical timeline
Visa brand approvalAbout 5 business days after Visa approves your card program
Apple's program review (Apple Wallet only)Up to 4 weeks
TokenizationAbout 10 business days. Google Wallet is handled by Visa directly within these 10 days, with no separate review

For brand approval and tokenization on both wallets, you provide the following:

  1. Mobile wallet metadata:
    • Card art: Reuse your physical card design, or send a new 1536×969px landscape .png (no chip, cardholder name, card number, expiration date, or rounded edges; include a white or Visa-blue Visa logo).
    • App icon: A 100×100px .png, color to the edges, no rounded corners.
    • Card label: What the card is called when added to the wallet.
  2. Visa Cardholder Agreement: Complete yours. All end customers must agree before adding a card.
  3. Privacy Policy & Terms: Publish these on your website. Visa surfaces these via "Additional Information" in the wallet.
  4. Apple contact: One person from your organization who can sign the Apple Non-Disclosure Agreement (NDA). See Apple's Program Review for the details to send.

Apple's Program Review​

Before Visa can tokenize your BIN for Apple Wallet, Apple reviews your card program through the Apple Partner Hub, Apple's portal for card programs. This is a one-time review for manual provisioning, separate from the push provisioning approvals later in this guide.

What you provide: One point of contact for your organization who can sign the Apple NDA, with their:

  • Full name
  • Mobile number, which must be able to receive text messages from Apple
  • Email
  • Business address

What happens next: Visa manages the review for you:

  1. Unit sends Visa your program review request, with contacts for your organization, your bank partner, and Unit.
  2. Visa submits the request in the Apple Partner Hub and adds those contacts to it.
  3. Apple verifies each contact by text message and may follow up with requests for review, confirmation, or signature, including the Apple NDA. Your contact should respond promptly. Apple typically replies within 24–48 hours of receiving what it needs, so the overall timeline depends largely on how quickly each party responds.
  4. Apple's review through the Partner Hub can take up to 4 weeks. Once Apple approves your program, Visa opens a tokenization project, which typically completes within about 10 business days.

Next Steps​

Once tokenization is live, end customers can add their cards to Apple Wallet and Google Wallet manually. To let them add a card with one tap from your app or website, continue to push provisioning and choose a build path.