Loads purchase.
Tries to enrich original request with memberId from LoyaltyCard service, if loyaltyCardId has value and memberId is null, then saves the purchase.
Body
The purchase data.
Globally unique purchase ID. it's recommended to compose it based on transaction date and time, store ID, and POS ID. Recommended pattern: {yyyymmdd}{hhmmss}{ssss}{ppp}, where sss - store ID, ppp - POS ID. Example: 202307101706440023011
1 - 64Id of store where payment is done.
1 - 128Local store currency code. ISO-4217 currency code - 3 characters, for example, DKK, ISK, EUR etc.
3Total price of purchased products with discounts and taxes applied. Can be negative in case when total price of returned items is greater than total price of purchased items. Decimal amount with '.' as float separator. Example: 105.55
Total amount of taxes (VAT) included in price. This amount should be included in PurchaseLoad.Api.CQRS.Commands.LoadPurchase.LoadPurchaseCommand.TotalAmount. Decimal amount with '.' as float separator.
Date and time of the purchase in UTC. Example:'2020-04-14T11:00:00Z'.
Date and time of the purchase in store local timezone. Example:'2020-04-14T13:00:00'.
The list of purchased products.
Id of member who performed purchase.
36The identifier for an external discount card that is not linked to the loyalty app. By default, this field should be empty. If populated, then bonus calculation will be skipped as the customer has received external benefits.
Identifier for the loyalty card. Used for member identification if this value is provided but memberId is not specified.
36Order identifier, whithin which the partial receipt was generated. This field is related to e-commerce transactions.
The total amount used for calculating bonuses. This amount excludes items like lottery, tobacco, alcohol products. By default, this field should not be passed, so that Bonus Calculation service automatically excludes ineligible products. If passed, this value will be used to calculate the basket-level bonus. The value should be a decimal with '.' as the separator (e.g., 10.25).
All payment methods which user used to cover the purchase.
List of discounts applied to purchase/products. Optional. If no discounts were applied it should be missed.
List of summarized tax details.
Unique identifier of POS in Lobyco payment service. Recommended pattern is '{storeId}_{posId}'.
Set of key-value pairs that you can attach to an object. This can be useful for storing additional client-specific information about the object in a structured format. By default, this field should be skipped, unless otherwise agreed upon during integration.
Pos, SelfCheckout, ScanAndPay, Online Id of POS where payment was done
Member's phone number
Response
OK