Credentials
| Field | Where to find it |
|---|---|
| API login ID | In the Authorize.net merchant interface under Account → Settings → API Credentials & Keys. |
| Transaction key | Created on the same page. Creating a new one disables the old one after a while, so update OrderCard promptly. |
Use a sandbox account (from developer.authorize.net) for a sandbox gateway. Test connection authenticates without a transaction.
Operations
| OrderCard | Authorize.net |
|---|---|
| Purchase | authCaptureTransaction |
| Authorize | authOnlyTransaction |
| Capture | priorAuthCaptureTransaction |
| Void | voidTransaction |
| Refund | refundTransaction (OrderCard supplies the card’s last four digits, which Authorize.net requires) |
| Verify | authOnlyTransaction for $0.00 |
Authorize.net refunds only work on settled transactions, usually the day after the charge; before that, void it.
Surcharging
OrderCard adds the surcharge from the rate set on the gateway. By default it also sends Authorize.net’s dedicated surcharge field, which only TSYS-processed accounts accept. If your processor refuses it, turn off Send the surcharge field on the gateway; the surcharge is then included in the amount only.
3-D Secure
A 3-D Secure result sent with a charge goes in Authorize.net’s cardholderAuthentication element: the ECI as authenticationIndicator and the authentication value as cardholderAuthenticationValue. Authorize.net uses these for Visa and Mastercard on Chase Paymentech, FDMS Nashville, Global Payments and TSYS, so check that your processor is one of them. Values it refuses come back as response reason codes 116 to 118.