• Combined Auth and Clearing Transactions to a Single File – This feature consolidates relevant data from both Auth and Clearing in a single file for Network Agnostic (Non-Visa) transactions.
• Using Indirect Merchant Country for Cross-Border Validations – Visa will verify the accuracy of Issuer and Merchant country data from the onboarding profile by comparing it with the transaction authorization feed.

• Plan Cancellation – The current plan cancellation functionality encounters a problem when a full Plan Cancellation request is made at the clearing level. This feature corrects the Plan Cancellation functionality to avoid this validation logic error.
• Retaining Cross-Border Authorization Amount Details – For Cross-Border transactions, this feature will provide non-converted Auth/Clearing source amount and currency to Issuers.

• Removed Profile from Search Cardholder Enrollment API – Removed Cardholder search by Enrollment Profile ID as a conditionally required option.
• Updated vPlanIDRef in Matched Eligible Installment Plans API – The vPlanIDRef field in Matched Eligible Installment Plans API response was updated to a required field.
• Replaced Request and Response Header – The x-correlation-id was replaced as ex-correlation-id in the request and response header.

• Debit Enrollment, Unenrollment – These features allow Visa to extend its solution to Debit Cardholders.
• Debit--Plan Cancellation & Reports – VIS wants to increase cardholder base and transactions by offering installments to Debit Cardholders.
• Debit--Notifications – VIS will send notifications to Issuers about various events to inform and alert them to facilitate their operations.
• Enabling Payment Schedules for Debit Transactions – This feature creates payment schedules for Issuers handling Debit transactions.
• Enabling Daily Reports on Payment Schedules for Debit Transactions – This feature enables daily reports of payment schedules for Issuers handling debit transactions.
• Reducing Balance Rate Calculation – This is a new functionality introduced to manage eligibility responses for plans based on the Reducing Balance Rate (RBR) indicator at the plan level.
• Removed Several API Endpoints from Issuer Guides – Several API endpoints were either deprecated or removed from the code.

• Different Service Fee for Cross-Border Transactions – This feature allows Visa to charge both the Issuer and Partner (Payfac, Acquirer, Merchant) a different service fee for Cross-Border transactions.
• Changes to Issuer Fee Reports for Cancellations – The ACQUIRER_TO_ISSUER fee field will be added to Issuer Fee Reports to enable clients to track Non-Merchant Funded plans through Issuer Fee Reports.
• Multiple Same-Tenure Plans at Checkout – This feature allows Issuers to surface multiple same-tenure, same-type plans with various pricing options for their cardholders.
• Islamic Installment Plan Support – In order to be compliant with Shariah Banking principles, a new field, Islamic Plan, has been introduced at a plan level. The Issuer will be able to indicate whether the Installment Plan is Conventional or Islamic.
• Rules Governing Bilateral Plan Hierarchy--Plan Precedence – Updated the description of plan precedence under Rules Governing Bilateral Plan Hierarchy so that the hierarchy policy is detailed clearly.

• Updated Phone Number Validations in Client Onboarding API – The phone field was updated to have the additional information on country-specific format allowed for Phone number.
• Updated vPlanIDRef in Matched Eligible Installment Plan API – The vPlanIDRef field in Matched Eligible Installment Plans API response was updated to a required field.

• Merchant Disablement by Issuers – Issuers can manage which Sellers/Indirect Merchants can offer installment plans. In regions such as U.K., due to regional laws, Visa allows Issuers to control which Merchants they can engage with and the plans that they can display. 
• Different Service Fee for Cross-Border Transactions – This feature allows VIS to charge both the Issuer and Partner (Payment Facilitator, Acquirer, Merchant) a different service fee for Cross-Border transactions, so that we can collect the correct Service Fee amount. 
• Bulk Onboarding of Merchants on Visa Installments – Acquirers will be able to onboard Merchants using a self-serve interface to upload Indirect Merchants. 
• Updated cardBrand Options – The cardBrand field, to describe the network brand, was updated with a new NON-VISA option along with other card types. When no value is set (or the field is not returned), the cardBrand will be treated as VISA. For Non-Visa Account Range enrollment, cardBrand will be returned as NON-VISA.

• Fee Reports for Cross-Border transactions – Cross-Border Fee Reports will be given in local currency.
• Cross-Border Identifiers – Added Cross Border identifiers on various reports. 
• Updated Character Limit on Promotion Code – Τhe maximum value of Promotion Code/PromotionCode is updated from three characters to a two-character limit. 
• Combined Fee Amounts – Clients can benefit from a new feature that combines the installment amount and the consumer funded fee and upfront fee as a separate value, allowing clients to present the value without computation and satisfy the legal requirements for the region.
• Mastercard Credentials – Updated note to explain Mastercard Transaction ID.
• Updated transactionAmount Field – Updated the transactionAmount field descriptio to include foreign exchange rate conversion logic.

• Plan Acceptances Search Batch File, Issuer Fee Report, Issuer Exception Report, and several API Calls – Added a new Cross Border field to indicate Cross-Border capability.
• API Updates and Additions – Added a new version of the 403 Error Message to block transaction assocation calls for Post-Purchase. Added a Note on PAR field for select APIs regarding LCM updates. Clarified DateTime fields on truncating the millisecond part of the timestamp.
• Removed Pre-Purchase and Ledger Content – Removed prePurchaseOptin object and related pre-purchase content. Also removed ledger-related content.

Visa Installment Solutions has been enhanced to support the following features:

• Plan Cancellation API Enhancement to Calculate Elapsed Time - For pro-rated refunds (cancellation between 30 – 60 days), clients need to know the number of elapsed days to effectively compute the prorated funding fees being refunded. The Issuer Fee Report, notification payloads, and the Plan Acceptance Search API have been enhanced to include clearing dates and last refund dates. Therefore, when a Plan Acceptance or Installment Transaction is partially or fully cancelled, Issuers may be able to calculate elapsed time and prorated funding fee amounts so that they do not need to wait for billing reports to compute applicable funding fees. The Issuer Fee Report has two new columns: Cancelled Date Time and Clearing Date Time.
• Clearing Transaction IDs Matched for Post-Purchase Transactions - In 21.10, the Post-Purchase functionality has been enhanced to have the Issuer-provided Clearing Transaction IDs matched. For During-Purchase, the fallback to use Auth Code to obtain a Clearing match was already in place in case the Authorization Transaction ID is not matched. Based on the Clearing Transaction ID match, the Authorization matching step is skipped and Issuers should expect to see Post-Purchase Plan Acceptances to be marked as Confirmed after the Clearing is matched.
• Enhancement to Installment Transaction Notifications - External Client ID has been added to V2.0 Plan Acceptance and Installment Transaction status change notifications, which addresses a gap for the Issuers on behalf of relationships with Processors in V2.0 Push Notifications. Installment Transaction status change notifications have been enhanced to include additional transaction-level information so that Issuers may refer to the notifications for information related to multiple-clearing use cases. Additional details include Transaction ID, Auth Code, Transaction Amount, Clearing Amount (after clearing), and Currency Code (after clearing).
• New Issuer Exception Report - Visa Installment Solutions has been enhanced to provide a daily exception report which currently covers three exception scenarios. The first exception scenario is for notification failures of Plan Acceptance and Cancellation notifications. The second exception scenario is for Installment Transaction confirmations where the Clearing is received after a time period where the Authorization has dropped off on the Issuer side. The maximum time period is specified on the Issuer profile. The third exception scenario is when the status of the notification is unknown and we do not know whether the client received the notification.
• PGP Encryption Support for Batch File Flows - The V2.0 Issuer Fee Report and Exception Reports have been enhanced to support both PGP and JWE encryption. When configured in DCP, clients will need to select at least one form of encryption but will have the option of selecting their preferred form of encryption for files from Visa Installment Solutions. For example, clients may select CSV with JWE encrypted PANs or PGP for PGP encrypted files with clear PANs.

Visa Installment Solutions has been enhanced to support the following features:

• Encryption Enhancement for V2.0 Batch Enrollment and Unenrollment Files - V2.0 batch enrollment and unenrollment files have been enhanced to support both PGP and JWE encryption. When configured in DCP, clients will need to select at least one form of encryption but will have the option of selecting either or both of PGP and JWE encryption for files from Visa Installments.
  
• Enhancement to V2.0 Business Reports – The Seller Fee Report, Issuer Fee Report, and Seller Transaction Report have been enhanced to support Plan Acceptance eCommerce scenarios and partial refunds.

• Post-Purchase Enhancement for V1.0 – V1.0 APIs have been enhanced to support post-purchase Installments on split-shipment transactions by allowing a single transaction ID to map to multiple clearing items. For V1.0 post-purchase Installments only, the amount passed in Plan Selection is now the clearing amount, not the authorization amount. Issuers must create a new a Plan Acceptance for each (any) clearing. 
• Updates to ledger management - Clearing Sequence number is added along with Transaction ID in LAAF file to uniquely identity the Ledger Entry however this change is off by default to ensure Issuer backward compatibility.

• Post-Purchase Enhancements – Both API v1.0 and API v2.0 have been updated to utilize determine Cardholder eligibility and installment payment amounts for Cardholders participating in Post Purchase Installment Plans will be billed according to settlement currency (Issuer’s currency and Cardholder billing currency), rather than authorization currency (Merchant’s currency) for Post Purchase Installment Plan purposes, for the transaction amount of all purchases placed on Post Purchase Installment Plans. As the settlement currency is the domestic currency for issuer, Tthis means that cross-border purchase transactions can beare expands the scope of transactions eligible for Post -Purchase Installment Plans to include transactions that were cross-border at the time of purchase.  Both API v1.0 and API v2.0 have been updated to utilize settlement currency enabled to include cross-border transactions for Post-Purchase installments as a result of enhancementsin to the Eligible Plans Match API, the Plan Selection API, and internal Visa processes that determine the Bbilling cCurrency (currency with which customer is billed) from transaction processing messages. This enhancement does not enable Cross-Border transactions for During Purchase.
• Batch File Enhancements –Batch files have been enhanced to support API v2.0 format for Cardholder Enrollment and Un-Enrollment APIs. Once issuers configure an Enrollment Profile in Visa Developer, issuer determines eligibility criteria for cardholder participation in Installment Plans. Issuer can then add and remove eligible cardholders from enrollment in specific Installment Plans through a batch process that pairs batch files with specific Enrollment/Unenrollment APIs.

• Post-Purchase Enhancements – Post-purchase API calls have been enhanced to enable recreation of a Plan Acceptance for a given transaction within 60 days of cancelling plan via Plan Cancellation API. This allows installments plans that have been cancelled to be restored.
• Batch File Enhancements – Enrollment Batch process has been enhanced to improve ability to recover from failures and improve enrollment performance for large batch sizes. Issuer Fee and Summary Report now separates Plan Acceptance confirmation and cancellation when both confirmation and cancellation occur on the same day.