Validate and store customer card details without charging by using zero-amount authorization requests for future payment token creation
A merchant may want to initiate a zero-amount authorization for the following reasons:
Storing card details for future use International payment systems strongly recommend sending a zero-amount authorization before storing card credentials for subsequent transactions.
Card verification A merchant may advance a potential customer to the next stage in the sales cycle by requesting their card details. This step confirms the card validity without any charges and also gauges the customer’s intent to finalize a purchase.
CVV verification To check the CVV of a stored card without charging the customer, use the
Guide
Build a resign payment form that uses stored card tokens to let returning customers complete checkout without re-entering card details.
Resign Form
with the stored recurring token. The customer enters the CVV in the Solidgate form, and a successful zero-amount authorization confirms the card details. This approach does not apply to Apple Pay and Google Pay payments, which do not use the CVV.
Card registration Occasionally, customers must register a card with their account. This action ensures that the card undergoes verification for potential future charges. An example would be registering a card at the outset of an evaluation period, ensuring its verification for possible charges when the period ends.
Free trial offers Merchants might offer their subscribers a trial period for their products at no cost or a discounted rate. This involves initiating a zero-amount authorization transaction before starting regular billing cycles.
Fraud prevention Assess the risk associated with a payment card before initiating high-value transactions. This reduces the likelihood of fraudulent activities.
Some issuing banks do not support zero-amount transactions and may decline the request even when the card details are correct.
Furthermore, a successful zero-amount payment does not guarantee subsequent charge requests receive approval, such as in cases of the
Guide
The customer’s card balance has insufficient funds.
3.02
Insufficient funds payment failure.
Request configuration
To perform a zero-amount payment, configure the payment request with the following settings:
amount
field to
0
If set to
null
, the default fallback value
0
be used.
The value of
0
in the
amount
field is valid in the request:
Otherwise, your request be declined with the
Guide
“Invalid data” code message is used for validation errors, with the reason for the validation triggering specified in the body (object error) of the response. Also, the code message “Order not found” is used as a decline on orders in case of API response to request on non-existent order.
2.01
General reason error code.
Authorization with 3D Secure
To process a zero-amount authorization as a
Guide
This process is designed to enable secure and reliable payment processing through the use of 3D Secure authentication, which provides an additional layer of security to prevent fraudulent transactions.
3D Secure payment,
pass the
force3ds
parameter as a boolean
true
value. Be aware that 3D Secure may be initiated either by your side or by the payment processor.
Authorization with auto-settle
Guide
Configure automatic settlement to capture authorized payments on schedule, reducing manual effort and accelerating your revenue cycle.
Auto-settle
feature is
not available
for zero-amount payment requests.
If the zero-amount payment is successful, the final order
Guide
Follow card payment orders through each processing stage with clear status definitions, available actions, and real-time event tracking.
status
displays the
auth_ok
value. Should the payment be unsuccessful due to an
Guide
This decline indicates that the entered card number is not correct and the customer’s account cannot be found.
invalid
or
Guide
This error occurs when the entered or stored card expiration date is invalid or has already passed.
expired
card, the final order status shows the
auth_failed
value.
Mastercard zero-amount authorizations can return verification_result.name_validation_result. Interpret the values in
Guide
Decode AVS, CVV, ANI, and Mastercard name validation results to verify cardholder address, security code, and name against issuer records for fraud prevention.
Mastercard name validation.
Note that if your payment provider does not support this API method, the zero-amount payment are be declined, resulting in the
Guide
An error occurred due to the processor not supporting the requested API method.
5.10
Processor does not support requested API method error code.
Void and settle
A zero-amount authorization is a specific payment and merchants must not
Guide
AThis process involves the merchant obtaining authorization to hold a Customer’s funds, Solidgate communicating with the acquirer to process the transaction, and the merchant settling the transaction.
settle
or
Guide
The process involves the merchant obtaining authorization to hold the Customer’s funds and initiating a void operation if needed.
void
such payments.
Should you attempt to settle or void a pre-existing zero-amount transaction, expect to receive the
Guide
“Invalid data” code message is used for validation errors, with the reason for the validation triggering specified in the body (object error) of the response. Also, the code message “Order not found” is used as a decline on orders in case of API response to request on non-existent order.
2.01
General reason error code.