Page Comparison

...

As documented here: Loyalty API - Getting Started.

Body

• loyaltyId <string>: Loyalty ID unique identifier of the loyalty user in UUID format.

• transactionId <string>: Loyalty order ID unique identifier of the loyalty transaction created in UUID format.

• channel <string>: “Restaurant”, “App”, or “Web”. Always use “Restaurant” for In-Restaurant orders.

• created <string>: string that represents the current date and time of the request.

• serviceMode <string>: service mode of the order being placed. This can be “EAT_IN”, “TAKEOUT”, ”DRIVE_THRU”, “CURBSIDE”, or “TABLE_SERVICE”.

• status <string>: status of the order that indicates if the order is still pending or if it has been completed. This can be “PENDING” for orders not yet completed and “CLAIMED” for orders that were completed.

• transactionDetails: object identifying order information from the request (POS or Kiosk):

  • currency <string>: the currency used in the market.

  • order: array identifying all products inside the order. each product is an object with these fields:

    • name <string>: name of the product.

    • price <number>: price of the product.

    • productId <string>: PLU of the product.

    • productType <string>: type of the product. This can be “combo”, “item”, “reward” or “offer”.

    • quantity <number>: number of times this product was ordered.

    • referenceId <string>: line ID of product

    • tax <number>: tax amount attributed to this product.

    • parentReferenceId <number> (optional): line id of parent product. Only relevant for children products (e.g. a coke drink that was ordered as part of a whopper medium meal combo).

  • payments: array with an object identifying payment information of the order:

    • amount <number>: total cost of the order in cents.

    • type <string>: type of payment method that was used during payment for order. This can be “CASH”, “VISA”, “MASTERCARD”, ”AMEX”.

  • 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”, this field should be used to identify the POS/Kiosk brand for analytical purposes.

...

• points <number>: this represents the number of loyalty points the user has. If the order has a status of “PENDING” and includes rewards, then this number already has those loyalty points temporarily deducted from total user’s loyalty points balance. If the order has a status of “CLAIMED” this is the final point balance of the guest after the order is completed.

• pointsEarned <number>: this represents the number of loyalty points the user has. If the order has a status of “PENDING”, then this number will always be 0 since we don’t update the guests earned loyalty points until the order is completed. If the order has a status of “CLAIMED” this is the total number of points that were earned in this order.

• pointsRedeemed <number>: this represents the number of loyalty points the user has. If the order has a status of “PENDING” and includes rewards, then this number is the total loyalty points temporarily deducted from total user’s loyalty points balance. If the order has a status of “CLAIMED” this is the final number of points that were deducted / burned in this order.

• loyaltyId <UUID>: Loyalty ID <string>: unique identifier of the loyalty user in UUID format.

• transactionId <UUID> <string>: unique identifier of the loyalty transaction created in UUID format.

• receiptCode <string>: autogenerated code for easy lookup of the order via support tool

• presentation (optional): object that returns Receipt content information set in Sanity here.

  • footer <string> (optional): this represents the content that will show in the footer of the receipt: Loyalty API - Receipts

  • header <string>(optional): this represents the content that will show in the header of the receipt: Loyalty API - Receipts

  • identifier <string>(optional): this represents the content that will show in the receipt to identify the order: Loyalty API - Receipts

  • pointsEarned <string>(optional): this represents the points earned that will show in the receipt of the loyalty order: Loyalty API - Receipts

  • totalPoints <string>(optional): this represents the total points balance that will show in the receipt of the loyalty order: Loyalty API - Receipts

...