Issuance PINs Integration Guide

Use the Issuance PINs API to enable electronic wallets and other financial accounts that do not typically accept a personal identification number (PIN) at point-of-sale terminals (POS) or automatic teller machines (ATM) to set up and use a PIN. The API validates and manages the lifecycle of these PINs.

Overview

The Issuance PINs solution enables external API users, such as Google with AndroidPay, to manage PINs for tokens that are loaded onto mobile devices.

You can create one PIN to share among multiple instruments, which can be tokens or cards.

Integration steps

Set up your development environment

Before you can integrate Issuance PINs, you must set up your development environment. After you get a token that lets you access protected REST API resources, you create sandbox accounts to test your web and mobile apps. For details, see Get started.

Then, return to this page to integrate Issuance PINs.

Create shared PIN

You can create a shared PIN that is associated with a card, tokenized card, or account.

To create a shared PIN for any of these instruments, include a user-provided PIN and the PIN profile name. The product configuration engine must configure this name.

Additionally, provide a PIN owner reference, which is a card number, PayPal account ID, or external account ID, for the instrument:

For more information about these parameters, see pin_create_request. To create a shared PIN, see create shared PIN.

Update PIN

You can update a shared PIN. For example, you might want to update the PIN number itself, the PIN profile name, or the PIN reference owner.

For information, see update PIN.

Show PIN details

You can show details for a PIN, by ID.

For details, see show PIN details.

List PINs

You can list PINs that match the search criteria. You specify search criteria through these query parameters:

For details, see list PINs.

Next

• Issuance PINs API reference