2 May 2025

Card issuing - Get started with card issuing

Docs

Your ultimate resource for card issuing is here! Dive into the latest detailed guide Get started with card issuing, meticulously crafted to provide you with everything you need to know about setting up card issuing on the Pismo platform.

This comprehensive guide offers clear step-by-step instructions for launching your card issuing program. It outlines the seven steps you take to get your card issuing program up and running.

• 1: Plan: Identify the integration decisions to consider.
• 2: Establish a framework: Build the foundational processes and permissions for your program.
• 3: Create your programs: Design your card issuing program.
• 4: Create accounts and customers: Add accounts and customers to use your card issuing program.
• 5: Create cards: Create your customized cards.
• 6: Test: Ensure your program works correctly before launching it.
• 7: Monitor: Continuously monitor your program’s performance and provide ongoing customer support.

Card issuing - Card network integrations

New

A new option was added to the available limits validation in ledger to allow customers to perform a dry run validation. In this case, the ledger validations are performed as a simulation to check if the account balance would be impacted, with no actual impact to the account balance. Dry run results are returned in the validation_results field in the anti-fraud payload. The dry run can be performed for SKIPPED and REJECTED statuses, for specific reasons. Details are included in the Rule list guide.

Seller management - Marketplace

New

The new Split transactions feature is now live. This feature allows for dividing a single transaction into different categories or assign portions to various accounts. This is particularly useful for handling shared expenses, allocating costs across different budget categories, or separating business and personal expenses. This new feature includes the following endpoints:

• Create split request
• Cancel split request
• List split requests
• Get split request details
• Get split request totals
• Get merchant balance

Accounts

Updated

For the Get account endpoint response, the blocked_amount field is always going to be null. To get this information, you can call List account limits and look at the held_funds field.

Balance configurations

Updated

In the balance configuration endpoints, the enum values for the amount field in the configs.scenarios.result object were updated (the principal_amount option was removed).

Flexible transaction controls

Updated

In the rules/Evaluation requested and audit/Evaluation requested events, the custom_code and evaluated_controls fields were added to the object.result object.

Updated

In the Account flex control created and Account flex control updated events, object field, the account_id field is now available.

Docs

The time_zone field now correctly shows up in documentation for the following endpoints:

• Update account flex control
• Update customer flex control

Ledger

Updated

The currency_code and currency_numeric_code fields are now available in the Account balance changed event and in the following endpoints:

• Get daily account balance limits
• List account limits
• Get related accounts

Migrations

Updated

Documentation for the Migrate on-us authorizations endpoint was updated with the new object InstallmentsDetails.

Updated

The object PostDisputeV1Request was added to the Migrate disputes endpoint.

Updated

The error message sent by the Migrate disputes endpoint was improved. This message is sent when the endpoint requires information about the clearing file that was previously provided by client.

Docs

The Migrations guide was updated with information about migrating balance controls and accruals.

Setup

Docs

The Program parameters guide was updated with additional information and corrections.

Transactions

Updated

The following error code was added to the Create transaction flow and Update transaction flow endpoints:

• ETRC04003: The provided amount type is already configured for the processing code

The following error codes were added to the Create transaction flow endpoint:

• ETRC04004: The provided transaction type is already configured for the processing code
• ETRC04005: The provided amount type conflicts with an existing configured amount type for the processing code

Transaction banking

Updated

The new 400 error message "Misconfigured administrative division" was added to the following endpoints. This error occurs when customers send the wrong data type in the metadata field from the Create holiday endpoint.

• Create earmark
• Update earmark
• Cancel earmark

Updated

The error message "Account has not finished onboarding" was added to the following endpoints. This validation error occurs when an account is not yet fully onboarded but begins to accept payments.

• Create earmark
• Schedule payment

Updated

The division_id field was added to the 200 and 201 response payloads of the following endpoints:

• Create division
• List division

Docs

In the Upload bulk file endpoint, step 2 in the Detailed flow in the description is now changed to “The server processes the request and responds with a 200 OK status, indicating that the file upload request is complete.“ Previously, it was “The server processes the request and responds with 307 Temporary Redirect instructing the client to forward the request to a pre-signed URL provided in the Location header.“

Docs

The following guides are now available:

• Back-value-dated transactions
• Future-value-dated-transactions

Docs

Additional information is now available in the File signature and encryption guide.

In the Before you begin section:

• When sending a bulk file, both the original file and the signature file must be included.
• The original file refers to the input bulk file.
• The original file must be encrypted using an AES key after it has been signed. You can request an AES key by calling the Get AES key endpoint.
• The original and signature files should have the extensions .original and .sign, respectively.

In the Signature file format section, the signature file is a text file containing a JSON object with the signature data, the JSON object contains the following fields:

• org_id: Tenant identification.
• signing_key_id: ID of the public key corresponding to the private key used to sign the file.
• bulk_id: ID of the bulk as specified in the original file.
• signature: Signature encoded in base64.

Card network integrations

Docs

The custom code for card inputted expiration date validation in the Rule list guide was updated to reflect the correct code of CED.

Docs

The Validation results example for Validation results data has been updated to represent a situation where flex controls are enabled. This is part of the Authorization validation rules for card network operations guide.

Direct network transactions

Fixed

The List authorizations endpoint was removed from the Authorizations API reference documentation as it is for internal Pismo use only.

Statements

New

The new section in the API reference - Features by account status - contains 3 new endpoints:

• Configure features by account status
• List features by account status
• Update features by account status

Updated

In the 200 response payload of the List account accruals v3 and List account accruals v2 endpoints, the new stop_accrual_reason field was added to the additional_info object.

Protection Bulletin

New

Protection Bulletin (PB) endpoints - Register card for Protection Bulletin and Create Protection Bulletin rule - were redesigned with specific objects for each network Pismo’s PB supports - ELO, Mastercard, and Visa. The Protection Bulletin guide was updated and moved to the Cards management section.

Lending

Docs

In the Loan repayment updated event, the required account_id is now documented correctly.

Merchants

Updated

The new Get merchant balance endpoint is now available in the Seller management - Transactions API. This endpoint provides an estimate of the available funds in the merchant account on a specified target date. It takes into account the scheduled merchant transactions in the specified marketplace to calculate the estimated values.

Pismo Control Center

New

Pismo Control Center now enables you to view, add, edit, and deactivate general ledger accounts.

New

Notifications in Control Center now support announcements. This type of notification communicates application updates, new features, or similar changes.

New

When a Control Center request fails, the error is reported in a popup message. The message includes a Report log with technical details that users may copy to include when making a service request.

Docs

The role descriptions table in the Access profiles and roles guide for Control Center was simplified for clarity.

Docs

The Processing codes and transaction types guide for Control Center was combined into one and updated.