Skip to main content
You can screen for prepaid cards to prevent customers from using these cards for certain transactions. For example, you can refuse prepaid cards as the payment method for recurring Subscriptions.

Using the ExtendedCardAttributes Subobject to Screen for Prepaid Cards

When working with Chase Paymentech, Worldpay (Vantiv/Litle), and Merchant e-Solutions payment processors, you can screen for prepaid cards using the ExtendedCardAttributes subobject of the PaymentMethod object. The ExtendedCardAttributes subobject returns auth response details from the payment provider. The value for the PrepaidCard data member indicates whether the card is prepaid. Possible values are: Y (true), N (false), or U (undefined). To screen prepaid cards in Vindicia Subscribe, perform a separate card validation using PaymentMethod.update or AutoBill.update. Below is a sample ExtendedCardAttributes response within the auth response for AutoBill.update:

Using the BIN Database to Screen for Prepaid Cards

You can also sign up for a third-party Bank Identification Number (BIN) Database service to identify the card type based on the card number. In this way, you can pre-screen cards before the cards are processed in Vindicia Subscribe. Consider this option when working with payment processors other than Chase Paymentech, Worldpay (Vantiv/Litle), and Merchant e-Solutions. Parent topic:Payment Management