If you have selected Authorize.Net as the Payment Gateway, follow the below steps:

Account Information 

1. Under Account Information, enter your API Login ID and Transaction Key.
   
2. Enter the Signature Key. Refer to the steps required to obtain it below these instructions.
3. Select the required Currency in which you wish to receive payments.
   
4. Enter the Payment  Amount. You can either set a fixed amount for payment or autofill the Payment Amount with a value from a form field.
   
5. Enter the Payment Method. You can either choose a Card or Bank Account for payment.
6. To test the payment gateway with your form, select Sandbox Mode. Payments made using the sandbox mode will not involve real transactions. To do this, you will need to create an account at https://developer.authorize.net/hello_world/sandbox. Learn More

1. Under Webhook Configuration, copy the Webhook URL (e.g., https://forms.zoho.com/zylker/zfauthnethook)
   
2. Log in to your Authorize.Net Developer dashboard.
   
3. Navigate to Webhook Configuration (Account > Settings > Notification Settings > Webhooks > Add Endpoint).
   
4. Paste the copied Webhook URL from Zoho Forms. Use it to configure the webhook.
   
5. Perform a test payment in Zoho Forms and check if the payment status updates automatically. 
   

1. Under Payment Information, specify the details to be shown in your Authorize.Net dashboard.
   

• You can change the default Description and merge form responses in the description by clicking the   icon and selecting the required fields.

• Under Mail Receipt to, you can select the required Email field from the form fields. Stripe will send the receipt of the transaction to this email address.

Customer Information 

1. Under Shipping Information, you can include the Name and Address of your customer by mapping them to the corresponding form fields. 
   

2. Under Billing Information, you can include the First Name, Last Name, Address, and Phone Number of your customer by mapping them to your form fields.

Steps to obtain the Signature Key

1. Login: Login to https://account.authorize.net/ using your administrator account.
   
2. Navigate: Navigate to Account > Settings > Security Settings > General Security Settings > API Credentials & Keys > Create New Key(s)  >  New Signature Key.
3. Submit the Request: Click the Submit button to proceed.
4. Verify Identity: Request and enter a PIN sent to your registered email address or phone number to verify your identity. 
5. Retrieve New Signature Key: Once verified, your new Signature Key is displayed. Copy this key securely for use in your integration or application.
   

Note: 

1. If the Signature Key provided is invalid, payment status will not be updated.  

2. On the All Entries page under Payment Transaction ID field, the Order ID appears when the payment process is initiated. If the transaction succeeds, the Txn ID is appended. If it fails, it is not appended. 

What’s different (New vs Old)  

Similar to obtaining the Signature Key in the latest version, the older version requires a Public Client Key. Log in to https://account.authorize.net/ with an administrator account, then go to Account → Settings → Security Settings → General Settings → Manage Public Client Key. In Create New Public Client Key, enter the answer to your secret question and click Submit. Your client key will be displayed as a string—copy and use it.

Why Switch to the Latest Authorize.Net Version 

1. Enhanced security: With the latest version, respondents pay on a secure Authorize.Net checkout page. Their card details are never entered on our form as in the old version, lowering the risk of data exposure. 
2. Flexible payment methods: Choose to accept Card, Bank Account or both. Old version supports Card payments only. 
3. Future support: The latest version receives updates and fixes; older versions are maintenance-only.
4. Cleaner data: The new version uses two fields for the Shipping Info - First Name and Last Name instead of a single name field. 
   
   

When configuring payment gateways, sensitive information like secret keys and tokens are encrypted before they are stored in our database and are never exposed to other third party apps.