July 2021

In July 2021 we clarified some events in the Events API, corrected a guide, added new guides, corrected a flowchart, increased the name length, updated a parameter description, added an error code for card activation, updated response schema descriptions, updated the Transaction Types enumeration, added a new error code for the PIN retrieval service and added new fields to the Auth API. Click July 2021 to see the details.

Clarified events in the Events API

In the Events API reference, we added more context to the descriptions of many of our events, including what triggers the event and which processes may elicit that trigger. One example is the CAPP: app_completed event, which is triggered by successful account creation.

We plan to add similar context to the remaining event descriptions soon.

Corrected About Card Transactions guide

The E-commerce section of the About Card Transactions guide erroneously stated that AVS checks with response code 85 were recorded in the CST as denied transactions. The text has been corrected to say that approved AVS checks are not visible in the CST but that denied checks are.

Corrected About Adjustments flowchart

On the Create adjustment workflow, we corrected the decision on the "Overdraft is successful" diamond and corrected the start of the overdraft subflow.

Card Transaction Scenarios guide

For Galileo clients only there is a new Card Transaction Scenarios guide that contains detailed examples of various transaction types such as preauthorization/completions (gas pumps), reversals, ATMs, international transactions, card loads, incremental authorizations, tokenization, and unmatched authorizations. Included is a narration of the sequence of events plus tables showing what data to expect from the Auth API, Events API, Program API, and RDFs. Ask your Galileo representative for the PDF.

Name length increases

The maximum character limits for the firstName, middleName and lastName parameters have been increased from 30 to 40 characters for these endpoints:

• Create Account
• Update Account
• Create Virtual Card Account
• Start Enrollment
• Update Enrollment

Debit/credit description updated

For the Create Adjustment endpoint, the description for the debitCreditIndicator parameter was updated to clarify that the account in accountNo is being debited or credited.

New error code

A new error code 467-06 was added to Activate Card to indicate that the card is in a status not permitted for activation by product parameter CRDBL. This error code is currently in limited production, so you might not receive it yet.

Response schema updates

The field descriptions for the response schema of Create Provisioning Request have been updated.

Updated Transaction Types enumeration

The Transaction Types enumeration now lists the transaction types for authorization and settlement transactions and shows which activity types are possible with each transaction type.

Guide added plus updates to existing guides

We added the About Card Transactions guide, which provides a tutorial on how card transactions work in the card-processing ecosystem, shows example transaction sequences and describes what you can expect from different merchant types. To complement this new guide, we've updated About Transactions and Transaction History to reflect the information in the new guide. Of especial interest are the revised Transaction sequence examples in the Transaction History guide, which include more information to help you track transactions across your system.

New error code

The PIN Retrieval Service has a new error code: 401. When an image is not found the error code is 404, and for all other errors the code is now 401.

New Auth API fields

To versions 2 and 3 of the Auth API we added two new fields to the amounts object: amt_til_limit and nearest_limit.

Guide added

The About Mobile Wallets guide provides instructions for setting up mobile wallets and explains how manual provisioning and push-provisioning work.