This topic describes getting started with the Pismo platform and the core objects that are configured during your onboarding process. Many endpoint calls address and interact with these core objects.

Basic component structure

The Pismo platform has a built-in object hierarchy. The following table describes the platform's built-in object hierarchy and their basic relationships.

Entities, Customers, and Accounts

The following diagram shows, at a high-level, the mapping of account customers to entities.

Core objects

📘

Field lengths and ranges

Specific field lengths and ranges are not detailed in the tables below. However, you can find that information in API endpoint reference documentation.

About initial setup

The first thing you need to do is work with Pismo to onboard your Organization and first Program to the platform. Once those are in place, you can start creating accounts and customers, issuing cards, and calling Pismo API endpoints.

Organization

Setting up your Organization (Org) requires you provide the following information, along with other information about your banking needs, to the Pismo implementation team.

Once created, your Org is assigned an identifier that is either referred to as a Org ID or Tenant ID and will look similar to this - TN-34778262-f4f0-464d-b4c6-a14e2dc6f4be. Most endpoints take this field as a parameter, usually in a header. You can use the Get org info endpoint to retrieve the information for your organization.

Program

After you have your org set up you can use the Pismo Console to create the first program associated with your org. Program attributes depend on the type of program. Program types are:

• Credit
• Debit
• Pre-paid

Each of the above types are issued either thru Visa or Mastercard and can be either full or zero-balance.

The following table shows Program information you need to provide during setup.

You still need to work with the Pismo implementation to set up a program - what you can configure through the Pismo Console isn't complete. For example, an issued card's initial status can be configured, but not through the Console.

Entity

Every customer has an associated entity object. If one isn't passed in the Create customer endpoint, then one is automatically created based on government document number. An organization can have multiple customer objects with different customer IDs all mapping to the same entity object, meaning they are all the same person or company. You can call Get customer to see a customer's entity object.

To search an organization's data using an entity ID, contact our Service Desk and request this.

An entity object has the following fields:

Account

You can create an account with the Create account application endpoint.

An account object has the following fields:

For more information on accounts, see the Accounts overview

Customer

An account customer can be either a person or a company. When you create an account, the first customer - the account owner - is also created. Accounts can have multiple customers, typically to accommodate primary and additional cardholders, but only one owner. Customers can also have more than one account.

Call the Create customer endpoint to add a customer to an account.

Person customer object

Company customer object

Other objects

Card

You can issue a card with the Create card endpoint.

A card object has the following fields:

Cards also come with associated mode object(s) for combination cards - cards that can be used for both credit and debit transactions. For more information, see Create a combination card with modes.

For more information on cards, see the Cards overview.