Rejection Handling Tab
The table below explains the items on the Rejection Handling Tab of the Add a credit card processing process screen. On this tab, you set up how to handle transactions rejected by the credit card processor.
Screen Item |
Description |
What would you like to do with permanent rejections? |
In this section, select how to handle permanent rejections, such as transactions with expired credit cards and credit cards reported lost or stolen. |
Export transactions that have a permanent rejection and remove them from the batch |
To remove transactions that have permanent rejections from the batch and create an export of the transactions, select this option. |
Export Definition |
If you select Export transactions that have a permanent rejection and remove them from the batch, enter the export definition to use. You can search for an existing export definition. From the Export definition Search form, you can also add a new export definition. For information about export definitions, refer to the Query and Export Guide. |
Also create a selection of the commitments to which the exported transactions apply |
If you select Export transactions that have a permanent rejection and remove them from the batch, select whether to create a selection of the commitments to which the exported definitions apply. You can use this selection to create targeted communications to constituents whose credit card transactions were rejected, such as to request updated credit card information. |
Selection Name + batch number |
If you select Also create a selection of the commitments to which the exported transactions apply, enter a name for the selection. The program adds the batch number to the selection name. |
Overwrite an existing selection if it has the same name |
If you select Also create a selection of the commitments to which the exported transactions apply, select whether to replace an existing selection with the new selection if their names are the same. |
Take no special action |
To leave transactions that have permanent rejections in the batch and not create an export, select this option. |
What would you like to do with provisional rejections? |
In this section, select how to handle provisional rejections, such as transactions of credit cards that exceed the maximum balance limit or are rejected due to a banking server error. |
Create a special retry batch of all transactions from this batch that are given a provisional rejection |
To create a batch that contains all the transactions from the batch that have provisional rejections, select this option. You can use the retry batch to try to process the transactions again, up to the maximum number of attempts. |
Maximum number of attempts (2-10) for these transactions: |
If you select to Create a special retry batch of all transactions from this batch that are given a provisional rejection, enter the number of attempts to process a transaction that is provisionally rejected. The attempt count is not applicable for transactions successfully authorized the first time the credit card process runs on a revenue batch. When a transaction is placed into a retry batch, the attempt count increases. After a transaction has been attempted the maximum number of attempts, it is handled as a permanent rejection. |
Treat the provisional rejections the same as permanent rejections |
To treat credit card transactions that have provisional rejections the same as those that have permanent rejections, select this option. If you select the option, the program does not create a retry batch, and all rejected transactions are handled as permanent rejections. |
Take no special action |
To leave transactions that have provisional rejections in the batch and not create a retry batch, select this option. |