PaymentVision 5.0.3 is now available in production. The purpose of this release is to introduce two enhancements (Card Filtering by Brand and BIN Data) and three functional changes (5030 Error Response, Account Use Preference Prompt, and Bank Account Owner Type).
Card Filtering by Brand
Card Filtering by Brand is an enhancement to PaymentVision’s Card Filtering feature that enables it to be configured at the brand level.
What is Card Filtering?
Card Filtering is a feature of both PayAPI and the PaymentVision Portal that enables merchants to enforce card acceptance restrictions by type (debit, credit) and issuing bank.
What’s New?
While Card Filtering enabled merchants to enforce card acceptance restrictions by type prior to this release, what’s new is merchants can now establish those restrictions at the brand level (e.g.; Visa, MasterCard, Discover, American Express).
How it Works?
PAYAGENT
- When a customer adds a card to their wallet, PayAgent first validates the card number
- If the card number is valid, PayAgent looks up the BIN
- PayAgent then takes the result and checks it against the merchant’s Card Filtering configuration
- If the card type is restricted for the card brand, PayAgent presents an error message
PAYAPI
- An integrated application (e.g.; PayAgent, PayWeb 2, PayIVR) sends PayAPI a ValidateFinancialAccount request
- If the card number is valid, PayAPI looks up the BIN
- PayAPI then takes the result and checks it against the merchant’s Card Filtering configuration
- If the card type is restricted for the card brand, PayAPI returns a 1013 rule violation response
Use Case
Card Filtering by Brand helps merchants who collect or refinance existing debt to comply with Visa rule 5.9.10.1. Under Visa rule 5.9.10.1, merchants who collect or refinance existing debt are required to register as a Limited Acceptance Merchant, a designation which limits acceptance to Visa debit cards only.
5030 Error Response
5030 is an error response introduced during our Wallet Management release which prevents a payment from being processed in cases where the token is associated with an un-registered financial account. Based on feedback from customers, we have determined that this error response is overly restrictive, particularly in cases where payment schedules are maintained within external systems. As part of this release, we are removing the 5030 error response.
BEFORE AND AFTER
| Before | If a customer re-introduces a financial account on PayWeb 2 or PayIVR and chooses not to save the account, any previously scheduled payments associated with the account will be rejected. |
| After | If a customer re-introduces a financial account on PayWeb 2 or PayIVR and chooses not to save the account, any previously scheduled payments associated with the account will continue to process. |
Financial Account Storage Preference
Financial Account Storage Preference is a feature introduced as part of our Wallet Management release that enables a user to specify how they would like a financial account to be stored within the system. As part of this release, we are changing the text used to prompt the customer for their preference in order to avoid any confusion as it relates to previously scheduled payments.
BEFORE AND AFTER
| Before | Would you like to save your account for future payments? |
| After | Credit Card: Would you like to save this credit card to your account?Bank Account: Would you like to save this bank account to your account? |
BIN Data
PaymentVision has added two new columns to its credit card account table as part of this release – card type and card issuer (a.k.a. BIN Data).
HOW IT WORKS?
When a credit card account is added to the system, PaymentVision will now lookup the BIN and add BIN Data to the record. PaymentVision has also, retroactively, updated existing records with BIN Data.
USE CASE
Adding BIN Data to our credit card account table lays the tracks for future BIN reporting.
Bank Account Owner Type
Bank Account Owner Type is a field within the Customer Enrollment website. As part of this release, we are changing the way in which this field is validated.
BEFORE AND AFTER
| Before | A user can register a bank account without specifying a Bank Account Owner Type (e.g.; business, personal). |
| After | A user is required to specify a Bank Account Owner Type (e.g.; business, personal) in order to register a bank account. |
USE CASE
Bank Account Owner Type will enable integrated applications to assign the correct ACH Standard Entry Class (SEC) code in cases where they process a mix of business-to-business and consumer-to-business payments.
