Skip to main content

General Guidelines

Monetary Values​

All monetary figures (e.g., sum, totalAmount, discount, etc.) within the API are:

  • expressed in the smallest currency unit (e.g., cents rather than dollars),
  • positive when representing charges to the customer,
  • negative when indicating discounts or deductions.

Displaying Balances​

Balances such as points or credit are returned using two fields:

  • monetary: the equivalent value in currency based on the business's conversion rate,
  • nonMonetary: the actual balance (e.g., number of points).

All balances are returned in the smallest units (e.g., cents). Integrated systems must divide these values by 100 for display, showing 2 decimal digits.

Tax-Exclusive Countries​

For markets where prices are displayed without tax, the integration must also report pre-tax values to ensure accurate benefit and payment calculations.

Purchase Reporting Rules:​

  • totalAmount, grossAmount, and netAmount must exclude tax.
  • The total tax should be reported in totalTaxAmount.

Date Format Standards​

All dates and timestamps in the API must comply with the ISO 8601 standard. Since UTC+00 is used, local systems should convert values for display purposes.

  • Date: yyyy-MM-dd
  • DateTime: yyyy-MM-ddThh:mm:ssZ (Z = UTC+00)

Synchronous Handling​

Except for voidPurchase and submitPurchase with status=open, all API calls are expected to be handled synchronously.

A timeout (recommended 5–10 seconds) must be implemented for network failures or delayed responses.

Asynchronous Handling Required:​

For submitPurchase calls with status=final, implement retry logic if:

  • A 5xx error is returned by Rekonect’s server,
  • A communication failure occurs.

We recommend 2 quick retries near the transaction time, followed by retries later in the day if necessary.

Handling Empty Fields​

Do not send fields with empty, null, or missing values. Only include fields with actual content.