Pismo platform onboarding
As a new customer, you'll follow an onboarding process to create your organization, access required tools and systems, and configure authentication. The exact steps vary depending on the products you plan to build—banking, card issuing, digital lending, and so on—but the overall process follows a common pattern.
Throughout the onboarding process, you work closely with your Pismo support team. This guide walks you through the steps you’ll take together.
Planning
Your Pismo support team will schedule planning sessions with you to shape your onboarding path. These sessions build on earlier conversations about your business goals, current challenges, desired products, and more.
Organization creation
Your support team creates your organization (known as your org) on the Pismo platform. The organization specifies your company’s details, such as its legal name, address, and time zone.
Some technical contextPismo uses core objects and has a built-in object hierarchy. The organization is the root object on the Pismo platform—a container for all your programs, accounts, and customers.
When your organization is created, you receive an org ID (also referred to as a tenant ID), which looks like TN-34778262-f4f0-464d-b4c6-a14e2dc6f4be.
Most API endpoint calls require this identifier, typically passed in the header.
For a comprehensive overview, refer to Core objects.
To create your organization, the support team will ask for the following information:
- Company's legal name
- Company’s preferred name on the Pismo platform (this can be the same as the legal name)
- Company’s document number, which is the unique company ID (such as a government tax ID or business registration number)
- Address
- Legal representative (person or entity)
- Email of the person at your company who can be contacted if necessary
- Currency
- Time zone
Pismo Service Desk access
The Pismo Service Desk is where you submit requests, resolve issues, and ask questions. To request access, refer to Request access to Pismo resources.
Keep these two points in mind:
- From the Settings dropdown, select Access request, then select Service Desk Portal.
- In the Description field, enter the email addresses of all users who need access.
Your support team can help if needed.
Test and production environment access
Your support team sets up access to two environments:
- Test environment—A non‑production environment used to test new and updated features. If you prefer to use your own test environment, let your support team know.
- Production environment—A live environment used to process actual customer data.
Additionally, you can use tools like Postman with Pismo's pre-built collections to test API endpoints before going live. For more information, refer to Test Pismo APIs with Postman.
Pismo Control Center access
Control Center is a web-based interface you can use to complete many tasks without using REST APIs. Your support team sets up your access. For more information, refer to Get started with Control Center.
Authentication set up
To access Pismo APIs, you generate an access token linked to your org ID, which provides server-to-server (S2S) authentication. Your support team works with you to set up the appropriate authentication method.
| Method | Description |
|---|---|
| Basic (client credentials) | Basic S2S authentication uses a server_key and server_secret, like username/password |
| OpenID Connect (preferred) | OpenID Connect (OIDC) provides greater security, supports multi-tenancy, and supports role-based access including third-party access. With OIDC, you generate public and private RSA key pairs, then generate a JSON Web Token (JWT) for each key pair. You share the public key with Pismo and sign the JWT with your private key. |
| OAuth2 | OAuth2 follows the RFC 6749 specification, providing secure token-based authentication. With OAuth2, Pismo obtains the access tokens using the Client credentials grant type. |
Additionally, Mutual Transport Layer Security (mTLS) is mandatory for all API calls to the Pismo platform to ensure compliance with security regulations.
For a comprehensive overview, refer to the Pismo platform security guide.
Next steps
With ongoing support and guidance from your Pismo team, you’ll set up your programs and accounts. Refer to the following guides to get started.
| Guide | Description |
|---|---|
| Get started with card issuing | Details how to set up and manage card-issuing programs, from integration and program setup to card creation and monitoring. |
| Get started with core banking | Outlines the steps for setting up core banking, including programs, accounts, and provider credentials. |
| Get started with transaction banking | Covers creation of transaction banking, including programs, organizational structures, calendars, and processing cycles. |
| Get started with demand deposit accounts (DDAs) | Describes how to configure demand deposit accounts for transaction banking. |
| Get started with digital lending | Explains how to configure the core components for digital lending, including products, processing codes, and repayment structures. |
| Get started with Seller management | Shows how to set up marketplaces, merchants, receivables, fees, advances, and settlements using Seller management APIs. |
For more general support, refer to the following guides.
| Guide | Description |
|---|---|
| Get started with the Pismo Developers Portal | Introduces how to use the Pismo Developer Portal and where to find key guides and reference. Includes an introductory video. |
| Get started with Ask AI | Describes how to use AI-powered search in the Developers Portal to find answers and related content. |
| Get started with Control Center | Covers how to access and use Control Center to build and manage payment and banking programs. |
Updated about 3 hours ago