Authorize

View as Markdown
The authorize request is the first step the merchant POS will call when the customer enters a fuel code at the pump or inside the store. 1. All independent requests will have unique transaction ids 2. The `authorized_flag` determines whether the authorization was successful. I.e. an HTTP 200 call with `authorized_flag: false` is considered a valid response (where the authorization is declined). 3. There are 3 ways to limit the authorization, please review the docs on limits. The authorize response will include a `voids_at` field which specifies when this authorization will expire. The POS must abide by this field and not allow capture calls after the deadline ends (typically 24 hours). This endpoint will not return products which are not listed in the `available_fuel` field.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.
merchant_idstringRequired
site_idstringRequired
transaction_idstringRequired
transaction_time_msintegerRequired
available_fuellist of objectsRequired
payment_codestringRequired
currencystringRequired

Response

OK
merchant_idstring
transaction_idstring
authorized_flagboolean
voids_atinteger
authorization_codestring
total_amt_limitdouble
currencystring
fuel_limitslist of objects

Errors

400
Bad Request Error
409
Conflict Error