Pismo cards collection

This collection allows you to test a basic use case for creating and managing cards using the Pismo endpoints. This collection assumes you already have some basic data in your organization such as a program configured with due dates.

Before you begin:

• Work with your Pismo representative to set up your organization and at least 1 program configured with due dates. See Core objects for more information and getting started. The Pismo Control Center allows you to do a lot of this setup through a convenient UI.
• Make sure you have the Pismo sandbox environment as the current environment and have updated the environment variables as detailed in the Postman collections guide.

Step 1 - Authenticate

All of the endpoints require an access token. So, before you do anything else, you need to get a token by running the endpoint based on your authentication method, basic or OpenID.

• For basic authentication, call Platform > Authenticate > Get basic authentication access token
• For OpenID authentication, call Platform > Authenticate > Get OpenID access token

Running these endpoints automatically saves the access token as a local variable in the collection and this access token is then used in all the calls within the Platform folder. Access tokens expire quickly and can result in a 401 Unauthorized response message. If your token expires, run the endpoint again to get a refreshed token.

Step 2 - Test non-account-specific endpoints

Use the following sequence of calls to test endpoints that do not require an account ID. These calls walk you through what is needed to create an account.

1. Platform > Programs > List Programs
   Running this call updates the program ID variable (program_credit_id) in the collection variables. The program ID is required to create an account.
2. Platform > Programs > Get program due dates
   Running this call updates the due dates variable (dueDates_credit_id) in the collection variables. A due date is required to create an account.
3. Platform > Acquisitions > Create an account application
   Once you have an account, you can create an account token - an access token encoded with a Pismo account ID. This is required for calls in the account specific folder of the collection.

Step 3 - Test account specific endpoints

Use the following sequence of calls to test endpoints that require an account ID. These calls walk you through a few basics that you can test to get acquainted with how the endpoints work for cards.

NOTE: Some endpoints only work with programs that allow those configurations, for example, if the program does not allow cash-in transfers, that endpoint does not work.

1. Account specific > Authenticate with account > Get basic authentication access token or Get OpenID access token with accountID
   These calls get a new token that includes the accountID. This endpoint is saved separately from the earlier authentication token and is used for all endpoints in the Account specific folder.
   For more information about account tokens, see Endpoints that require an account-specific token.
2. Account specific > Accounts > Personal Data > Register a new phone
3. Account specific > Cards > Physical > Create plastic card
4. Account specific > Cards > Physical > Get card PCI info
5. Account specific > Payments > Make a transfer > Make a Cash-In transfer
6. Account specific > Payments > Create payment request
7. Account specific > Payments > Pay a payment request