Credentials
| Field | Where to find it |
|---|---|
| Client ID | From the credentials email Deluxe’s integrations team sends. |
| Client secret | From the same email. |
| Partner token | The merchant GUID from the same email. |
Deluxe issues separate sandbox and production credentials. Test connection requests an access token and checks the partner token.
Operations
| OrderCard | Deluxe |
|---|---|
| Purchase | POST /payments (sale) |
| Authorize | POST /payments/authorize |
| Capture | POST /payments/complete |
| Void | POST /payments/cancel |
| Refund | POST /refunds |
| Verify | POST /paymentmethods/avs |
Deluxe answers declines with HTTP 200 and a non-zero response code; OrderCard reports them as declines. Its responses carry no standard decline codes, so OrderCard reads the decline reason from Deluxe’s message.
Surcharging
OrderCard adds the surcharge from the rate set on the gateway, includes it in the amount, and records it on the payment as Deluxe’s surcharge fee.
3-D Secure
Deluxe’s API has no 3-D Secure fields for card payments. A 3-D Secure result sent with a charge is recorded on the transaction with forwarded set to false, and the charge goes to Deluxe without it.