Page Comparison

...

• identifier <string>: OTP (6 digit code) or Loyalty ID in UUID format.

• posVendor: object identifying system making the request (POS or Kiosk):

  • transactionId <string>: the POS transaction identifier.

  • storeId <integer>: uniquely identifies the store where the guest is identifying from.

  • terminal <string> (optional): identifies the POS or Kiosk terminal used in the restaurant

  • operator <string> (optional): identifies the POS operator (only applicable for orders made on a POS terminal)

  • posType <string>: identified the type of POS or Kiosk system making the request. This value must have been previously agreed between the vendor and RBI, so that the correct integration configuration is applied. In most cases, this will be set to a value of “Partner”.

  • supportingPos <string> (optional): in case the posType is “Partner”used mainly by kiosk vendors, this field should be used to identify the POS/Kiosk brand for analytical purposeswill need to refer to the POS vendor of the store the kiosk is sending the request from.

Example request

{
    "identifier": "123456",
    "posVendor": {
        "operator": "300", // operator id
        "supportingPos": "POS vendor name (optional field)"
        "posType": "Kiosk vendor name",
        "storeId": "9999",
        "terminal": "0", // terminal id
        "transactionId": "000000000257"
    }
}

...