--- title: "Authorize.Net" slug: "authorizenet" description: "Learn how to enable and configure a third-party payment gateway." updated: 2024-09-27T13:24:29Z published: 2024-09-27T13:24:29Z canonical: "docs.zilliant.com/authorizenet" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zilliant.com/llms.txt > Use this file to discover all available pages before exploring further. # Authorize.Net Learn how to enable and configure [Authorize.Net](https://www.authorize.net/resources/how-payments-work.html) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A29%3A00Z&se=2026-11-11T13%3A29%3A00Z&sr=c&sp=r&sig=s9vzczB%2FjNE8z8T7oeAc7vhLGlno%2Fbv6qycdNBTMEZY%3D). Authorize.Net is a third-party payment gateway for accepting card payments from customers. ## Enable payment gateway for Commerce 1. From the application left navigation area, select **Administration**. 2. From the top navigation bar, select **Master Data Management**. 3. Scroll or search to locate **Setting Boolean** and select it from the list. 4. Select **Enable Payment Gateway Integration**. 5. Set the **Setting Value Boolean** switch to **YES**. ## Create an Authorize.net sandbox account 1. Go to [Create sandbox account](https://developer.authorize.net/hello_world/sandbox.html) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A29%3A00Z&se=2026-11-11T13%3A29%3A00Z&sr=c&sp=r&sig=s9vzczB%2FjNE8z8T7oeAc7vhLGlno%2Fbv6qycdNBTMEZY%3D) page. 2. Follow instructions to create a sandbox account. Tip To obtain the production account, contact [Authorize.Net](https://www.authorize.net/resources/how-payments-work.html) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A29%3A00Z&se=2026-11-11T13%3A29%3A00Z&sr=c&sp=r&sig=s9vzczB%2FjNE8z8T7oeAc7vhLGlno%2Fbv6qycdNBTMEZY%3D) directly. 1. Sign into your sandbox **Account**, then go to **API Credentials & Keys**. 2. Enter the **API Login ID**. 3. Obtain the new **transaction** and **signature** keys. ## Create destination on the AWS platform 1. From the application left navigation area, select **Administration**. 2. From the top navigation bar, select **Destination Configuration**. 3. Create a new destination and define its properties. For the following properties, use the values from the sandbox account you created in the previous step: - anet.algorithm - anet.loginName - anet.signatureKey - anet.transactionKey ![Destination config](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Destination%20config.png?sv=2026-02-06&spr=https&st=2026-11-11T12%3A29%3A00Z&se=2026-11-11T13%3A29%3A00Z&sr=c&sp=r&sig=s9vzczB%2FjNE8z8T7oeAc7vhLGlno%2Fbv6qycdNBTMEZY%3D) ## Customize payment gateway behavior 1. From the application left navigation area, select **Administration**. 2. From the top navigation bar, select **Master Data Management**. 3. Scroll or search to locate **Groovy Script** and select it from the list. 4. Choose one of the following options: - **Option 1** 1. Select **Payment Gateway Submission Params**. 2. In **Script File**, attach the Groovy script, then select **Save**. This Groovy script sends additional data to Authorize.net, such as the billing address or shipping cost. The script should return a nested map containing keys and values in the format expected by Authorize.net, as defined in [Payment transactions](https://developer.authorize.net/api/reference/index.html#accept-suite-get-an-accept-payment-page) ![](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/external-link-svgrepo-com.svg?sv=2026-02-06&spr=https&st=2026-11-11T12%3A29%3A00Z&se=2026-11-11T13%3A29%3A00Z&sr=c&sp=r&sig=s9vzczB%2FjNE8z8T7oeAc7vhLGlno%2Fbv6qycdNBTMEZY%3D). - **Option 2** 1. Select **Payment Gateway Handle Status Check Result**. 2. In **Script File**, attach the Groovy script, then select **Save**. This Groovy script is called when Authorize.net has processed the payment for the order. The script stores the transaction ID. Data from Authorize.net is made available in the script in the `payload` variable. ## User experience when making direct payments On the checkout and re-order screens, users can choose from two types of payments: - **Purchase order** - **Direct payment** ### Direct payment The user enters credit card details on the direct payment screen. ![Direct payment](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Direct%20payment.png?sv=2026-02-06&spr=https&st=2026-11-11T12%3A29%3A00Z&se=2026-11-11T13%3A29%3A00Z&sr=c&sp=r&sig=s9vzczB%2FjNE8z8T7oeAc7vhLGlno%2Fbv6qycdNBTMEZY%3D) Tip For testing, use the following details: - **Card Type**—Master Card - **Credit Card Number**—5555 5555 5555 4444 - **CVN**—Any 3 digits - **Expiration Date**—Any future date