bLoyal API Documention and Samples |
The SalesTransaction entity is passed into the CalculateSalesTransaction method and the SubmitSalesTransactoin method. This consists of the transqaction header, line items, shipments (if applicable) and payments used on the transaction.
Restricting anyType
Contains elements as defined in the following table.
Component | Type | Description |
---|---|---|
Channel | string | [Optional] This will default to the Channel assigned to the device. If you provide it, it should be WebStore, Club, POS, Kiosk, Mobile, etc... |
Created | dateTime | When the sales transaction was created in your local system. It's important to use your sales transaction date and time so that sales reporting in bLoyal will match when the sale was actually processed. |
Customer | TransactionCustomer | The basic information about the customer on the transaction. If no customer was set to the transaction then this can be null. bLoyal will automatically resolve the customer based on the fields you fill out. |
ExternalId | string | Your transaction number |
Lines | ArrayOfSalesTransactionLine | The line items for the transaction. |
Payments | ArrayOfSalesTransactionPayment | The payments used. This is only required when submitting a transaction. This is optional for CalculateSalesTransaction |
Shipments | ArrayOfSalesTransactionShipment | If this transaction was for a shipment order then you need to enter the shipment(s). |
StoreExternalId | string | If you system does not have a unique transaction number across stores then you should fill in this field which is the unique transaction number for the given store. |
Token | string | The bLoyal generated transaction token. |
Name | Type |
---|---|
SalesTransaction | Element |