Connecting Authorize.Net

Setup

1. Click on Connect Authorize.NET

2. You will be redirected to the Authorize.net site to login.

3. 

4. On success, you will now be redirected to finalise the setup options.

Extra Settings:

Payment Methods

You can set up other payment methods like ACH that you might have enabled on your account.

Address Verification Setting

For AVS you will need to ensure that you have this configured in your authorize.NET portal.

Webhooks (must read)

When configuring a connection to Authorize.NET, Shuttle wants try to configure itself as a “webhook endpoint” on your Authortize.NET account. It requests notifications for the following events:

"net.authorize.payment.fraud.approved"
"net.authorize.payment.fraud.declined"
"net.authorize.payment.authorization.created"
"net.authorize.payment.authcapture.created"
"net.authorize.payment.capture.created"
|“net.authorize.payment.refund.created”
“net.authorize.payment.void.created”

This provides support for the following use cases:

• Transactions held for review due to a merchant fraud rule. These transactions will show up as “In Progress” in Shuttle, in either a UNRESOLVED or PENDING status. Without webhooks enabled the merchant is responsible for manually marking these transactions as approved or declined in Shuttle in addition to Auth.NET. With webhooks, the merchant is only required to approve the transaction in Authorise.NET, and it will be automatically synced to Shuttle.
• Gateway instructed captures, voids and refunds. If the merchant logs into Authortise.NET and manually captures an authorisation or refunds a payment, this would not show in Shuttle. By enabling webhooks we will automatically reflect these actions and pass them onto the source system.

To configure webhooks the merchant must configure a “Signature Key” on Authorize.NET before, and update Shuttle with that configuration. Unfortunately Authorize.net does not enable Shuttle to do this on a merchant’s behalf.

Tip: “Webhooks not configured” warning does not impact your ability to process payments.

To do this, follow the below instructions:

1. Select “Account” Menu
2. Select “API Credentials & Keys”
3. 
4. Select “New Signature Key” and “Submit” (do not disable your old signature if you are using webhooks with another system)
5. 
6. Complete the Auth.NET verify your identify
7. 
8. Record the “Current Signature Key” 
9. 
10. Enter this into the “Signature Key” field in Shuttle and “Save”
11. 

Shuttle will then install itself as a webhook endpoint on your account and trigger a webhook via requesting a transaction on an invalid card number that will be declined. 

Upon receiving the webhook, the “UNVERIFIED” label will be replaced with:

• VERIFIED: If everything was successful
• UNSIGNED: If the signature key did not match, in this scenario please follow the steps again.

Please note, accounts where Webhooks are UNVERIFIED or UNSIGNED will ignore webhook updates.