topic Re: Authorization and future capture are showing up as two transactions on bank statement... in Integration and Testing

Authorization and future capture are showing up as two transactions on bank statement...

FredFredrickson — Wed, 29 Nov 2017 22:02:50 GMT

We have a POS system we've been developing for a restaurant, and one of our difficulties with Authorize.net is the inability to modify a transaction for TIPS after a capture, so our solution was to pre-authorize the card for a small percentage more and then capture the final bill total at the end of the night during closing.

The final capture is usually less than (but can be equal to) the pre-auth amount depending on the size of the tip.

We use authOnlyTransaction and priorAuthCaptureTransaction to accomplish this.

The problem is, once that capture goes through, the pre-auth is still sitting in the customer's online banking if they used a debit card (as credit). I called the bank to confirm that the pre-auth will disappear naturally on its own, and that it doesn't affect their available funds (or cause over-draws) but I'm worried that a $15 bill will hold $15 for the pre-auth, and then $15 for the capture, and the customer will see -$30 in total until that pre-auth vanishes. Though it fixes itself in 24-hours, it's confusing and might spark extra customer complaints.

Are we doing something wrong that the capture doesn't immediately take the place of the pre-auth?

Re: Authorization and future capture are showing up as two transactions on bank statement...

FredFredrickson — Fri, 01 Dec 2017 14:49:12 GMT

I'm hoping somebody here has an answer for this!

Re: Authorization and future capture are showing up as two transactions on bank statement...

Anurag — Fri, 01 Dec 2017 19:16:38 GMT

Hi @FredFredrickson We are checking with the internal team on it and will update .

Re: Authorization and future capture are showing up as two transactions on bank statement...

bhav — Fri, 01 Dec 2017 20:46:49 GMT

@Anurag, @FredFredrickson

If you are using TSYS/Vital processor, you can use the Tips functionality supported for both EMV and non EMV transactions through API channel.

Tips functionality is not supported for Non TSYS/Vital Processor.

Showing the transactions in the customer statement is handled at the processor side.

For the restaurant scenario, if there are > 10 customers in a table, there would be auto-gratitude added to the receipt.

If that is the case, you can use authcapture by passing Tip amount through the API - CreateTransactionRequest.

Eg: API:

<name>XXXXX</name>

<transactionKey>XXXXX</transactionKey>

</merchantAuthentication>

<transactionType>authCaptureTransaction</transactionType>

</creditCard>

</payment>

<order>

<description>Product Description</description>

</order>

<tip>

<name>Tip amount</name>

<description>Tip amount</description>

</tip>

</transactionRequest>

</createTransactionRequest>