AnsweredAssumed Answered

Preventing Card Declines

Question asked by kdill00 on Jun 18, 2019
Latest reply on Jun 24, 2019 by livmorgan

Like • Show 0 Likes0
Comment • 1

Hi, I have a quick question, we have some customers using Vantiv Express hosted payments page for online transactions. These customers in question are movie theatres, so some people purchase tickets online in a couple batches. It seems that if they do that, the first one is fine, but a lot of times the bank will decline the next immediate transaction. This doesn't seem to occur with other processors we integrate with. Is there anything we can add to pass along to reduce these declines?

Thanks for your time.

livmorgan Jun 24, 2019 8:09 AM

Correct Answer

Hello,

This is likely caused by our duplicate logic that is automatically enforced on all merchant accounts upon initial boarding. Our duplicate logic is: same transactionAmount, same cardNumber, same transaction category (sale, refund, etc.) within 25 transactions.

Now, to override or disable this feature, the following must be done programmatically in your calls to Express (in your case, within the TransactionSetup request):

1. Pass <DuplicateCheckDisableFlag> as 1/true

Set this flag to true to disable the duplicate checking feature on the host. If this flag is set to true no duplicate checks will be performed for that transaction. This is a per transaction request feature.

2. Pass <DuplciateOverrideFlag> as 1/true

Set this flag to true to override the duplicate checking feature if the response from the host indicates a duplicate transaction has been attempted. In other words, if you send a transaction that was determined to be a duplicate by the host,set this flag to true and resend the same transaction to bypass the duplicate checking feature on the host. This is a per transaction request feature.

For reference, detail around our duplicate logic and these fields in particular can be found on page 23 of our Express API.

See the reply in context

No one else had this question

Outcomes

1 Reply

livmorgan Jun 24, 2019 8:09 AM
Unmark Correct
Correct Answer
Hello,

This is likely caused by our duplicate logic that is automatically enforced on all merchant accounts upon initial boarding. Our duplicate logic is: same transactionAmount, same cardNumber, same transaction category (sale, refund, etc.) within 25 transactions.

Now, to override or disable this feature, the following must be done programmatically in your calls to Express (in your case, within the TransactionSetup request):

1. Pass <DuplicateCheckDisableFlag> as 1/true
- Set this flag to true to disable the duplicate checking feature on the host. If this flag is set to true no duplicate checks will be performed for that transaction. This is a per transaction request feature.
2. Pass <DuplciateOverrideFlag> as 1/true
- Set this flag to true to override the duplicate checking feature if the response from the host indicates a duplicate transaction has been attempted. In other words, if you send a transaction that was determined to be a duplicate by the host,set this flag to true and resend the same transaction to bypass the duplicate checking feature on the host. This is a per transaction request feature.
For reference, detail around our duplicate logic and these fields in particular can be found on page 23 of our Express API.
2 people found this helpful
Like • Show 1 Like1
Actions

Preventing Card Declines

Outcomes

Related Content

Recommended Content