November 2025
In November 2025 we clarified a product parameter, added regex to an enum, added a new enum, clarified push-provisioning setup, added new endpoints, updated a DE061 subfield, added a new Auth API field, deprecated some parameters, clarified billpay timing, added account-closure reasons, removed some mobile-wallet params, and automated a refund-check process. Click November 2025 to see the details.
Updated parameter definition
We have updated the definition of product parameter FFTID to clarify that when it is set to Y, any supported idType is valid for Galileo's integrated ID verification process. When it is not set, only idType: 2 (SSN) is valid.
Regex for customer IDs
To the Customer ID Types enumeration we added the regex for each field.
Instant-issue statuses
The Get Bulk Card Order and Verify Instant Issue Card endpoints return card statuses that are specific to instant-issue cards. We've included links to the new Instant Issue Card Statuses enumeration.
Push-provision clarification
In the Setup for Push Provisioning guide, we reorganized some sections to make it clear that for all methods, you must start your relationship with Apple Pay by sending an email to apple-pay-inquiries at apple.com, and then if you want to implement web provisioning, you must contact Apple again to gain access to the Apple Business Register.
New endpoints
We have added two new token-management endpoints to the Reference:
DE061 update
In the DE061 Subfields enumeration, for Subfield 10 (Cardholder-Activated Terminal Level), we added the value 8, representing remote terminal transactions.
New Auth API field
If you subscribe to Visa’s provisioning score, you can receive the risk score associated with a token in the visa_token_score field on the Auth API.
Deprecated parameters
We have deprecated these product/program parameters and removed them from API documentation:
- CCODE — Currency code for transactions
- CIPEV — Test real customer names in CV.
- GTCIP — Gateway related
- IDSSN — Require SSN for enrollment
- NUMLD — Max number of loads per account
Billpay timing clarification
We have added information to detail when the billpay process performs balance checks relative to when amounts are adjusted from the account.
Account closure reasons
We have added new values for the closureReason parameter on the Modify Status endpoint. These values are also returned by ACST: account_status_change.
Temporary parameter removal
We have temporarily removed the parameters for the enhanced provisioning rules from the documentation pending further testing.
New refund-check automation
In the Account Holder Refunds guide, we previously explained that funds for canceled checks are returned to the refund account, but they're not necessarily returned to the original closed account. We have updated the back-end process so that for any canceled, expired, or voided check, the funds are returned to the refund account and then they're automatically moved to the original closed account. This automation eliminates the need to transfer funds manually from the refund account to the original account when reissuing a refund check.
