Skip to content
Myver logo Myver logo Myver

What is a Receipt?

A Receipt is a structured transaction record showing what was purchased, how each item was priced, and how the final amount was paid. It includes business details in the header, itemized purchases with any modifiers, calculated totals, and the payment methods used. Its purpose is to provide clear, auditable proof of the transaction for both customer and merchant, so Myver keeps the structure intact end to end.

The example below provides a visual reference for understanding how a full receipt is structured when represented in JSON:


1Store issuing the receipt

ACME Quality Apparel

42 Market Street, Dublin D02 XF85

2The header gives essential information about the transaction context.

Receipt #

9883-401204

Date

2026-07-29 13:39

Operator

Michael S.

Cash Register

Till #2

3Line items are the individual products or services listed on a receipt.

Premium Cotton T-Shirt

Qty: 2 @ 29.99 ea.

Discount: €9.99

€49.99

Classic Denim Jeans

Qty: 1

€79.99

4Totals represent the summary values calculated at the end of a receipt.

Subtotal

€139.97

VAT (23%)

€32.19

Total

€172.16

5Payments on a receipt show how the customer settled the amount due. This section lists each payment method used — such as cash or card payments.

Payment Method

Visa ending in 4242

Thank you for your purchase!

For returns and exchanges, please keep this receipt.

Structure

Section titled “Structure”

Receipt layouts vary by merchant, brand, and integration. Some include customer profiles or loyalty IDs, while others stick to line items and totals. Regardless of format, we render the data as-is so it faithfully matches what the source provides.

The sections below walk through each part of a receipt in more detail.

Section titled “Header”

The header captures the transaction context — when it occurred, which store and cashier processed it, how it was identified, and any operational notes such as register IDs or receipt status.

{
  "storeId": "st-33MxMppykHWC9eb3tSjWqWEK8qg",
  "created": "2025-01-01T12:34:56+00:00",
  "orderId": "25-20338",
  "receiptId": "9883-401204",
  "status": "Paid",
  "cashier": "Michael S.",
  "cashRegister": "Till #2",
  "printed": false
}

Line Items

Section titled “Line Items”

Line items form the heart of the receipt — each entry captures a purchased product or service, how it was sold, and any adjustments applied.

A typical line item includes:

  • Quantity and unit of measure
  • Unit price
  • Modifiers such as discounts, surcharges, or customizations
  • Product identifiers (GTIN, SKU, or internal codes)
  • Total line amount (unit price × quantity ± modifiers)

Example JSON representation

Section titled “Example JSON representation”

lineItems is an ordered array, and every element renders in the same order on the receipt. Each element follows the structure below:

{
    "id": "1",
    "description": "Premium Cotton T-Shirt",
    "item": {
        "sku": "71-5077",
        "gtin": "6987927150770",
        "unitPrice": { "gross": 29.99, "vat": 6.89, "currency": "EUR"},
    },
    "quantity": { "value": 2, "unit": "each" },
    "modifiers": [
        {
            "type": "discount",
            "amount": { "gross": -9.99, "vat": -2.29, "currency": "EUR" }
        },
        {
            "type": "customization",
            "description": "Size: Mens Large"
        }
    ],
    "lineAmount": { "gross": 49.99, "vat": 11.49, "currency": "EUR" }
}

Totals

Section titled “Totals”

Totals capture the monetary breakdown of the transaction — subtotals, VAT, discounts, freight, prepaid balances, loyalty redemptions, and the final amount due. Seeing each category separately makes it easy to understand how the payable amount is derived and to surface helpful summaries.

A receipt can include as many totals as the integration provides, and our platform never recalculates or adjusts them. We display the breakdown exactly as it arrives from the source.

Example JSON representation

Section titled “Example JSON representation”

totals is an ordered array, so keep the sequence aligned with how you want to display the monetary breakdown. Each element follows the structure below:

{
    "type": "vat",
    "description": "VAT 23%",
    "sum": {
        "amount": 32.19,
        "currency": "EUR"
    }
}

Payments

Section titled “Payments”

Payments document how the customer settled the balance. A single receipt can include multiple tenders — card, cash, gift cards, store credit, mobile wallets, or any method supported by the merchant.

Example JSON representation

Section titled “Example JSON representation”

payments is an ordered array as well, and multiple entries allow you to describe split tenders in the order they occurred. Each element follows the structure below:

{
    "paymentType": "card",
    "paid": {
      "amount": 159.00,
      "currency": "EUR"
    },
    "paymentTypeLabel": "Visa",
    "paymentAccountReference": "V0010056422073825495104907179",
    "retrievalReferenceNumber": "123456789012",
    "acquirerReferenceNumber": "ARN9988112233",
    "systemTraceAuditNumber": "123456",
    "transactionId": "389563057",
    "lastFour": "4242",
    "approvalCode": "048236",
    "terminalId": "TERM-02397173",
    "terminalSlip": "APPROVED\nVISA\nAmount: 159.00 EUR\nAID A0000000031010"
}