Month: January 2020

Transaction declined by Authorize.net but payment deducted from my card

Scenario:

The payment was declined with the message: “The Transaction has been declined because of an AVS mismatch. The address provided does not match billing address of cardholder”.

The buyer, however, received the text message from their bank that the transaction has been completed but at the same Dryfta shows the payment for the Order as Declined.

Explanation:

If the card used is a debit/checking card and it fails the AVS checks, the bank will still deduct the funds since the bank approved the transaction. The Authorize.net payment gateway declines the transaction due to AVS failure but the bank does not know this.

 

The cardholder would have to wait for the authorization to expire (seems to vary bank to bank) before the funds are returned to their account.

 

Since the transaction never settles, the merchant has no way to “refund” or “void” the transaction.

Summary:

When you get a decline due to AVS mismtach the customer is not charged. What they are seeing is a pending authorization which will eventually drop off.

Solution:

Go to your Authorize.Net Merchant Interface (Fraud Detection Suite > Enhanced AVS Handling Filter) and turn off the fraud screening settings so it does not decline transactions when the address doesn’t match.

Authorize.net Credit Card Numbers for Testing

You may use the following credit card numbers to run tests on your Authorize.Net account.

    370000000000002    American Express Test Card
    6011000000000012   Discover Test Card
    5424000000000015   MasterCard Test Card
    4007000000027      Visa Test Card
    4012888818888      Visa Test Card
    4222222222222      Visa Error Test

The last testing card number is used to generate errors. This card is intended to return errors and should only be used if that is your intent. For example, you should use that number if you’re testing your site to see how it will respond to Authorize.Net errors.

Expiration date: Use any expiration date after today. If a CVV is required use any three digit combination (four digits if you’re using American Express).

Important: These are not real credit card accounts and will not generate an approval if your account is in live mode. They will return a decline in live mode and an approval in test mode.

How to apply different prices based on location (i.e. if you’re in the US you get one rate, if you’re in Uganda, you get a different rate)?

To apply different prices based on location (i.e. if you’re in the US you get one rate, if you’re in Uganda, you get a different rate) :


Go to Tickets & Fees to create a sample ticket type.

Then go to Form builder > Attendee registration form (with tickets) and create a country field.

Finally, go to Discount Codes Manager and create a discount code and set it to be valid for selected countries only for selected ticket types.


As a prospective attendee, you would go to the website and select your tickets you would like to purchase, fill up the form and enter the discount code in the Apply discount code field. That would give attendee a discounted rate on that ticket type’s purchase.

How to use iPay payment gateway to collect payments on my Dryfta event website?

To collect payments using iPay payment gateway, you need to set up iPay payment gateway under your Dryfta event platform:

Enable iPay to collect payments.

Enable Test mode if you want to run test transactions before start collecting real payments.

Enter the iPay key and vendor ID provide to you by iPay. You can find it from under your iPay Merchant dashboard.

Apart from collecting payments through credit card, you also have the option to enable additional payment options.

Important Notes:

iPay payment gateway Phone number is required.

Billing section should remain enabled since this is where the Phone number field is.

Email addresses with “+” sign is not accepted by iPay.

iPay is only available for Kenyan Shilling.