Refunds using Full Card Data (stored)

Individual Refunds

Individual refunds are easiest when you can refund to a credit card on file. This is possible if

• You keep encrypted data in the database for all patrons by using Schedule D with a reasonable retention period -or-
• You are using merchant profiles and a profile has been created for the patron because they used the credit card to buy something -and-
• You are allowed to do independent refunds by your merchant provider.

Mass Refunds of tickets to Events

You can do mass refunds if you have card data stored in the database if the patrons card data meets the individual criteria above.

Possible Errors doing Refunds with Full Card Data

We recommend doing the refunds first, then authorizing during end of day. This gives you more control over the authorization process. Typical issues that can arise are:

• Credit card rejected - you will need to call the patron
• Independent Refunds - you might see these if they are enabled by your merchant provider.
• Linked Refunds - you might see some of these errors if independent refunds are not enabled.
• Shredded Card Errors - the system might create a payment for a shredded credit card. Naturally, this will be declined. The card can be entered manually during end of day.