October 2026
In October 2026 we explained military address support, clarified CNP and CVV2 behavior, updated Auth API info and recipes, clarified unmatched reversals, added a new product parameter, deprecated an endpoint, changed duplicate-transaction responses, corrected some codes, added fields to the Auth API, updated check-issue timing, upgraded the documentation site and standardized the templates across the Events API.
U.S. military address support
We added an explanation of how to support U.S. military addresses during onboarding and with ship-to addresses.
CNP and CVV2 behavior
We clarified that in some CNP cases, the CVV2 is missing when the merchant keeps the COF.
Nullable fields in the Auth API
We reviewed the nullable property of the Auth API fields (v2 and v3) and made corrections.
Auth API v3 Recipe updates
We added the program_id and product_id fields to all Auth API v3 Recipes. We also updated a few more fields such as adding the tar_info object to tokenization requests.
Unmatched reversals
We clarified system behavior in the case of unmatched card-transaction reversals to show the difference between STIP and non-STIP transactions.
Tokenization bypass check
We have added the BPTKC product parameter to the mobile wallet setup options to skip some checks during tokenization when cardholder data is not collected. It is similar to BPAVS, except that it applies to non-instant-issue products.
Deprecated endpoint
We have deprecated the Get Savings Interest endpoint. Instead, use Get Interest.
New duplicate-transaction behavior
For the Create Payment and Create Adjustment endpoints, we have changed the behavior when the system detects a duplicate endpoint request. If the first endpoint request was successful but you did not receive a response, you might resend the request and get status_code: 24 (duplicate transaction) in response. We are now including the data from the successful first request in the payload of the status_code: 24 response so that you won't need to perform a separate lookup to see if the original request was successful.
Corrected Account Feature Values page
To the Set Account Feature Values page we added 32 (overdraft account linking) and corrected the description for 31 (display preferred name on card only).
Corrected code for Visa Direct AFT A2A Reversal
We have corrected the trans_code for Visa Direct AFT A2A Reversal to show ADvf (correct) instead of ADvF(incorrect).
Digital payment data in the Auth API
We have added two new fields to the Auth API inside the digital_payment_data object:
digital_service_provider_detail— Parsed DE104 SE4 subfields, to complement the raw value indigital_service_provider.digital_authentication_data_detail— Parsed DE104 SE5 subfields, to complement the raw value indigital_authentication_data
We also corrected the description for the digital_payment_data object to say that it includes both subelements 4 and 5 of DE104. Previously it had mentioned only SE4.
Paper check timing
We have updated the paper check sections of Creating a Billpay Transaction to indicate that checks are now printed and mailed within 2–3 business days of initiating the payment instead of the next day. This change owes to a change in check-issuing vendors.
Upgraded documentation site
We upgraded this documentation site to offer better usability and richer functionality. For now, this only includes slight changes to the overall look and feel. We'll update this changelog as we roll out other improvements.
Standardized event templates
Effective October 6, 2026, SoFi Tech Solutions introduced standardized templates across the Events API and we have updated our public documentation to reflect these changes.
The scope and triggers for the events are unchanged; only the fields returned in the request body have changed. If your events were set up before standard templates, some fields you receive today have a different name in the standard template. The value is the same; only the field name changes.
Please note the following impacts to your integration:
- Existing integrations: Your current events template configurations are now frozen and can no longer be edited, but they will continue to function without interruption.
- Modification requests: Moving forward, any requests to modify an existing event will require you to first migrate to the new standard template.
We informed all clients of this policy change on August 19, 2026. Contact SoFi Tech Solutions if you have questions or need further assistance.

