1 July 2023
AccumulatorAuthenticationAuthorizationCorporate bankingDocumentationEventsFlex controlsMerchantsMigrationsPaymentsSeller management
Highlights
📍Accumulator API
New Accumulator API that can be used for creating an accumulator configuration that can be used to create an accumulator fee model. An accumulator keeps running totals for specified transaction types. Fees are applied to these totals based on an associated fee model.
📍Authentication updates
Pismo now supports the following authentication updates:
- Multiple public keys for the same Organization. This means that you can set up authentication using a specific public key to access a predefined set of endpoints within your Organization.
- Authentication using both public/private key and server key/secret methods. When moving to the production environment, you need to generate a pair of public and private keys for the API during onboarding.
📍Authorization timeline event
New authorization_cancellation_reversal-1 timeline event is now available and has been added to the list of timeline events.
📍Corporate banking updates
- Bank statements API has been refined and the new Get account balance history endpoint is now available.
- Earmark endpoints have been updated to focus on
earmark_id
as primary tracking ID.
📍New collection
On Sample project with basic authentication, the new Postman collection includes the following updates:
- Updated Branded authorization simulation endpoint:
POST {{baseUrl}}/networktransactions/v1/authorizations
- New Clearing simulation endpoint:
POST {{baseUrl}}/networktransactions/v1/authorizations
- Updated Branded authorization simulator endpoint to automatically generate an alphanumeric 6 digit code and store it in a variable.
- New Clearing simulation endpoint under CreditCardPurchaseSimulator, which uses the stored authorization code to clear the authorization without the user having to manipulate the collection.
📍New timeline endpoint
New List the events in an account timeline using a cursor endpoint replaces List events from an account timeline (deprecated) and [List the events in an account timeline using a cursor (deprecated).
📍New Org endpoint
New Retrieve Org data endpoint replaces Get Org info (deprecated).
Updates and fixes
📍Authorization code update
On Validation codes for authorization events, for custom authorization code FR2, VISA now returns N7, instead of 82.
📍Event updates
Added min and max values for the fields on the following events:
📍Flex controls updates
- The maximum number of flex controls that you can create per account, customer, or card is 200. If this number is exceeded when creating customer or account flex controls, the platform now returns the 409 error.
- On all flex controls endpoints, added the
code
field on the responses that return an error and marked theerror_code
field as deprecated.
📍Migration updates
On Migrate accounts, deprecated the collection_status
field.
📍Payments updates
- On the Create processing code endpoint, the new
is_external
field allows you to indicate if the operation should be validated against an acquirer external to the Pismo platform. This field is also available in the List processing codes endpoint. - On all Payments endpoints, added the
code
field on the responses that return an error and marked theerror_code
field as deprecated. - On the Cancel transfer endpoint, added the
authorization_datetime
field. - Partial cancellations are now supported. On the Cancel forced operation endpoint, the new
amount
field allows you to enter optional full or partial amount to cancel, which cannot be more than the original transaction amount. - On the Cancel forced operation endpoint, correctly marked
cancel_fees
as optional and added the following examples to the 400 error response:- Amount cannot be negative or zero.
- Amount should be less than or equal to the amount of the original transaction, and greater than 0.
- Partial cancellation with the associated fees was already made
- Updated Cancel transfer and Cancel forced operation guides to explain cancel fees behavior on the Pismo platform.
- On the platform-authorization-1 event, updated order of the fields, added the
cancellation_reason
,original_authorization_confirmed
andraw_message
fields, added descriptions to enum values in theresponse_code
field, and updated field names and descriptions forauthorization_id
andoriginal_authorization_id
.
📍Seller management updates
On Create creditors operation, added a new field processing_code
and made operation_type_id
not required.
Documentation
📍Data and reporting
- In all Data events guides, removed the URL column as redundant.
- Added new Transactions data events guide.
- On the Transactions ISS report files guide, corrected the
Authorization_ID
field and added theAuthorizationType
field.
📍Digital wallets documentation
New Card tokenization process and onboarding guide details card tokenization process on the Pismo platform.
📍Merchant documentation
- On Get transaction, in the
merchant
object, updated description of thestate
field to indicate that, in some cases, this field can indicate the country code of the merchant. - On Create merchant transaction and Create reversal transaction, added link to the Merchant transaction created event.
📍Migration documentation
- On Migrate accruals data, added a description under
values
>type
to explain when certain values should be sent when a client pays less than the minimum amount on the invoice. - On Migrate transactions, in the
migration
object, updated description of theauthorization_id
field.
📍Pismo Console documentation
Documented a condition where the process of creating a user in the Pismo Console neither confirms success nor reports a failure.
📍Platform documentation
- The Accounts limits guide has been redesigned to provide additional details about limits and their applicability to credit and debit accounts.
- On the Hold funds guide, added clarification about setting the
operation_type
toHOLD_FUNDS
.
📍Seller management documentation
- In Seller management, renamed the Creditors section to Creditor operations.
- On Create link between merchant and marketplace and Delete link between merchant and marketplace, corrected a typo in the URL from
marketplace
tomarketplaces
.
📍Settlement guide
New Settlement guide illustrates how the settlement process works.
📍Timeline documentation
In the Timeline events overview guide, replaced the word “transaction” with “authorization” (authorize, cancellation, and refusal are authorization types).