1$ Authorization Charge

[pakit]

Hello,

we have started to use Authorize.net in our production environment and we are noticing that 1$ charged is applied to client's credit card. 

We are using the following transaction type:

<transactionType>authCaptureTransaction</transactionType>

Even if it seems that this amount is returned back to the client within some business days , we would like to avoid that the clients see this charge on their bank account.
Is there any way to prevent this amount to be charged ?

Could you please advice? is a quite urgent subject, thank you!

Regards.

[kabutotx]

Do you mean <transactionType>authOnlyTransaction</transactionType>?

authCapture actually charges the card.  authOnly verifies the card can take $1 and will lower their credit limit that amount for approx 24 hrs but will not collect it.

[pakit]

Hello,

currently we are using AUTH_CAPTURE_TRANSACTION, so you mean that if  we switch to AUTH_ONLY_TRANSACTION the 1$ will be not charged and only the  real amount to be paid will be collected?

If we use AUTH_ONLY_TRANSACTION do we need additional steps to collect the real amount to be paid?

Thank you.

[Renaissance]

@pakit

Yes, that’s exactly right. Auth only will authorize the card for the amount. And you do need an extra step. You have to manually capture the transaction in the merchant interface or via API call. You have a 30
day window to capture.

[kabutotx]

Adding to @Renaissance  answer.  Most people Auth Only $1 just to verify a card is valid when an amount is unknown.  If you know the amount you Auth Only for that amount and then capture later.  With Auth.net the capture of an already authorized amount is basically a free charge.  For example, my company takes an order and Auth Only for the amount.  When we ship, we Capture the amount (you can capture the amount or lower once). If there is a backorder we have to Auth Capture the next shipment.