Credentials
| Field | Where to find it |
|---|---|
| User ID | The API user in your Fortis portal. |
| User API key | That user’s API key. |
| Location ID | The location the charges belong to. |
Use the credentials of your Fortis sandbox for a sandbox gateway and your production credentials for a live one. Test connection reads your locations to check them.
Operations
| OrderCard | Fortis |
|---|---|
| Purchase | Keyed credit card sale |
| Authorize | Keyed auth-only |
| Capture | Auth complete |
| Void | Void |
| Refund | Refund |
| Verify | AVS-only |
Surcharging
Fortis decides surcharges from the credit card product of your location. After connecting the gateway, choose Sync surcharge set-up in the gateway’s menu (or POST /v1/gateways/{id}/sync). From then on OrderCard asks Fortis’s surcharge calculator for each charge and sends the subtotal and surcharge fields Fortis requires.
OrderCard still refuses surcharges for billing addresses in states that ban them, and sends a zero surcharge there. Fortis set-ups that run the surcharge as a separate transaction, or charge a flat or minimum fee, are not supported; the gateway shows why, and charges go through without a surcharge. Sync again whenever you change the surcharge settings at Fortis.
Refunds of surcharged payments
A refund of a surcharged payment sends the surcharge portion separately, in proportion to the amount refunded.
3-D Secure
A 3-D Secure result sent with a charge sets Fortis’s threedsecure flag. The authentication value goes in secure_auth_data, the protocol version in secure_protocol_version and the directory server transaction ID in secure_directory_server_transaction_id. Fortis has no field for the ECI.