As of the 7.2.3 release, you can obtain an account verification of a customer credit card by generating a zero-dollar authorization; however, some banks will reject a zero-dollar authorization. When that occurs, you can opt to process a $1 charge followed by a $1 void to obtain account verification. Personify identifies that a zero-dollar authorization is being rejected because it's a zero-dollar authorization (and not because of a credit card error) by the error code. Rejection of a zero-dollar authorization because it's a zero-dollar authorization returns an error code of “4” or “12”. Personify generates the zero-dollar transaction whenever account verifications occur, such as:
· Entering
a Credit Card of Record
When a credit card of record is entered, a record is created in the Cus_Credit_Card
and Cus_Credit_Card_Profile tables, and Personify attempts to process
a zero-dollar transaction to obtain a token that can be used for future
purchases by that customer. If an error code of “4” or “12” is returned,
then Personify processes a $1 charge and $1 void transaction to obtain
the token.
· Running CCP650 to Obtain Tokens
Processes scheduled payments linked to credit cards that have tokens
that will or have expired.
· Updating the Credit Card of Record’s Expiration
Date Before It Expires
If the credit card expiration date has not passed, then you can update
the credit card expiration date to the new expiration date, without entering
the credit card number.
· Updating the Credit Card of Record After
It Expires
To update the expiration date of a credit card after the expiration date
has passed, the customer is required to provide the credit card number
of the credit card, as well as the credit card type, new expiration date,
and the name on the credit card.
· Updating the Non-expired Credit Card Information
on an Unfulfilled Order
If a credit card is being used as a payment method on an order that has
not yet been fulfilled, on a payment schedule, or for a recurring fundraising
donation, and if the credit card expiration date has not passed, then
you can update the credit card expiration date on the order to the new
expiration date, without having to enter their credit card number. This
occurs on the Order Entry (ORD001), Donation Entry (FND002_Donation_Entry),
and Insertion Orders (ADV002_Insertion_Orders) screens.
· Updating the Expired Credit Card Information
on an Unfulfilled Order
To update the expiration date of a credit card after the expiration
date has passed, the customer must provide the credit card number, the
credit card type, the new expiration date, and the name on the credit
card. You must update the credit card information being used as the order
payment method on the Order Entry (ORD001), Donation Entry (FND002_Donation_Entry),
and Insertion Orders (ADV002_Insertion_Orders) screens.
If
your organization has different merchants for web and back-office credit
card transaction and allows customers to create/update a "credit
card of record" from the web, you must setup ONE receipt type
and add BOTH merchants to it with TWO different cash accounts. For more
information about receipt types and cash accounts, please see Defining
Receipt Types and Cash Accounts.
· Updating a Non-Expired Credit Card from
the Web
If the credit card expiration date has not passed, then you can update
the credit card expiration date to the new expiration date, without having
to enter the credit card number.
· Updating an Expired Credit Card from the
Web
To update the expiration date of a credit card, the customer must enter
the credit card number, the credit card type, the CVV number, the new
expiration date, and the name on the credit card.
Users
can only update the credit card of record when they are in the Shopping
Cart.
· Pre-Validating a Credit Card
The “Pre Validate Credit Card” credit card merchant parameter was added
with the 7.2.3 release to allow organizations to pre-validate a credit
card by generating a zero-dollar authorization before processing the credit
card for full authorization. The pre-validation is to test the CVV or
the AVS so that the customer has the opportunity to provide the correct
information. When this parameter is set to “Y” and if either “Ignore AVS”
= “N” or “Ignore CVV” = “N”, the system generates a zero-dollar authorization
to validate the account information before processing the credit card
for full authorization.