Full balance versus zero balance integration
The following table summarizes the differences between full balance and zero balance integration.
With full balance integration, Pismo handles most of the process. With zero balance integration, you are responsible for managing your customers’ balances and credit limits. For both, Pismo provides card management and authorization integration with Visa, Mastercard, and other network brands.
|Feature||Full balance||Zero balance|
|Product setup: organization, programs, authorization||X||X|
|Account, customer creation||X||X|
|Card creation and management||X||X|
|Card validations||X||X - some|
|Customized card validations||X||X|
|Authorization through Base I||X||X|
|Streamed data events||X||X|
|Streamed timeline events||X|
|Clearing Base II authorization||X|
|Account balance and limit checks||X|
|Credit and debit settlement||X|
|General ledger management||X|
|Replacement amount processing||X|
|Flex transaction controls||X|
Card creation and management
Card creation and management includes the following:
- Card lifecycle (create, update, cancel)
- Card embossing integration
- Virtual cards
- Tokenization (Apple Pay/Google Pay, Garmin Pay)
- PIN updates
- Network integration
- Base I authorization processing
See Card issuing with Pismo for more information.
During transaction processing, there are two types of card validations that take place:
- Stateless validations (PIN, CVV, entry mode, and so on).
- Stateful validations (account/card status, limits, ATC, and so on).
With zero balance integration, you get stateless validations, but not stateful validations.
To see the validations done for full balance versus zero balance, see List of validation rules.
Customized card validations
An issuer can customize some validations, including:
- Allow local currency to be used in international purchases
- Allow transaction using card magnetic stripe
- Check terminal capabilities (entry mode vs. terminal capability)
- Must verify cryptogram for contactless or chip transactions
- Allow no-CVV and PIN validation for the card not present transactions
- Disable Card Verification Method (CVM)
- Validate chip signature
- PIN max error attempts
- Application Transaction Counter (ATC) range validation
See your Pismo representative to implement customized card validations.
Clearing Base II authorization
Card networks send two types of authorization messages, created by two types of messaging systems: a single-message system (SMS) and a dual-message system (DMS). The clearing/base II reconciliation process handles these messages.
With zero balance integration, you are responsible for handling Clearing Base II authorization.
With full balance integration, the Pismo platform provides anti-fraud integration via a partner.
With zero balance integration, you are responsible for your own anti-fraud checks as well as account and balance checks. See Zero balance anti-fraud and validations integration.
Credit card balances and interest accruals are managed in cycles (billing periods). A statement corresponds to a single cycle. The first cycle begins the moment the card is activated. After that, the first full day of each cycle follows the closing date of the previous cycle. On the last day of a cycle, the cycle is closed, and a grace period begins. This grace period belongs to the next cycle. When the grace period ends, if the card balance has not been paid off, charges begin to accrue. For more information, see Understanding statements.
With zero balance integration, you are responsible for managing the statement lifecycle.
General ledger management
The Pismo platform uses accounts to keep track of money flowing into and out of a company's general ledger.
With zero balance integration, you are responsible for maintaining a general ledger.
With full balance integration, you have access to the accounting API, with zero-balance, you do not.
With zero balance integration, you are responsible for handling accounting events via an accounting script.
It's sometimes necessary to add or remove money from a customer's account to reconcile balance inconsistencies (to credit an account when a transaction fails to be delivered or to return money to the customer). For more information, see the Adjustments overview.
With zero balance integration, you are responsible for making adjustments. You can do this using the Create adjustment endpoint.
A transaction is a record of a purchase, transfer, payment, or manual adjustment. In most cases, a cleared authorization triggers creating a transaction. For more information, see the Transactions overview.
Transaction management includes the following:
- Create transactions
- Set up transaction types and processing codes
- Payments API access
With zero balance integration, you are responsible for creating a transaction after clearing an authorization. However, you cannot set up transaction types and processing codes.
Flex transaction controls
The Pismo platform provides flexible transaction controls that enable you to restrict a customer's financial operations. For example, you can set a maximum amount allowed for a certain transaction type.
With full balance integration, you use the Pismo API to restrict customers' financial operations. With zero balance integration, you are responsible for implementing such restrictions.
You must have processes in place that allow cardholders to refinance their credit card debt. To that end, your program must make the following options available:
- Installment advances – Used to settle future debt on the current cycle, rather than on a future cycle.
- Installment agreement – Used to refinance an existing credit card debt.
- Statement agreement – A contract that renegotiates all debt – past, present, and future.
With zero balance integration, you are responsible for providing refinancing options to your customers.
For more information, see Credit card refinancing overview
Updated 17 days ago