03-27-2018 11:22 AM
We recently migrated a merchant from CIM hosted forms to Accept Hosted, and we are wondering if there is a way to alter the "validationMode" so the merchant is not billed each time a customer adds or edits a payment method?
Here's a reference for CIM:
But I can't seem to find any documentation on this setting with Accept Hosted forms?
03-27-2018 04:06 PM
We have below setting for disbaling the validationMode
Specifies how the payment gateway will validate the customer's card prior to creating the profile. Either liveMode or testMode. Defaults to liveMode.
liveMode generates a transaction to the processor in the amount of 0.01 or 0.00. If successful, the transaction is immediately voided. Visa authorizations in liveMode use 0.00 for all processors. All other credit card types use 0.01.
Standard gateway and merchant account fees may apply to the authorization transactions. For Visa transactions using 0.00, the billTo address and billTo zip fields are required.
testMode performs field validation only. All fields are validated. However, fields with unrestricted field definitions, such as telephone number, do not generate errors.
If you set this parameter to testMode, a 1.00 test transaction is submitted using the Luhn mod 10 algorithm to verify that the credit card number is in a valid format. This test transaction is not authorized at the processor, and does not appear on the customer's card statement, but it will generate and send a transaction receipt email to the merchant.
If a validation transaction is unsuccessful, the profile creation attempt fails, and the merchant receives an error.
Note: liveMode requires a billing address. If you do not want to collect a billing address, you must use testMode.
03-28-2018 09:00 AM
Thank you for the response.
So the validationMode is on a per-profile basis, set at the time of creation?
Is it possible to pass hostedProfileValidationMode with updateCustomerProfileRequest, or change it globally for the iframe?
03-31-2018 05:29 PM
The validationMode is on a per-payment-profile basis, not per-customer-profile basis.
It goes with Create Customer Payment Profile
and Validate Customer Payment Profile
and Update Customer Payment Profile
As to createCustomerProfileRequest, validationMode should only be sent when there is payment data in the request. updateCustomerProfileRequest doesn't need this field.
Hope this helps! Thanks!