Receiving Receipts from Myver

Myver matches receipts to transactions in real time. When an end user pays at a participating merchant, Myver identifies the receipt and delivers it directly to the client.

Before you get started

Myver delivers receipts by posting a Receipt Delivery event to a URL you register. To register your webhook endpoint, please contact us here before proceeding. When a receipt is ready, Myver sends a POST to your registered URL with the receipt data in the body. Respond with 200 OK to acknowledge it — Myver will retry if you don’t. See the full Receipt Delivery schema for the complete payload reference.

How to receive receipts

There are two ways to receive receipts from Myver:

Receipt Subscription

A receipt subscription automatically delivers receipts every time an end user pays at a participating merchant — no action required per transaction. It relies on a Payment Account Reference (PAR), a unique identifier tied to a payment card rather than a specific card number, meaning it works whether the end user pays with the physical card or a digital wallet such as Apple Pay or Google Pay. After the client has obtained consent from the end user, the PAR is registered with Myver, linking the payment card to the end user. If you don’t have a PAR, see Transaction Matching.

curl -i "https://api.prod.myver.tech/v1/subscriptions/par" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -d '{
        "par": "12345678912345678912345678912",
        "reference": "CUST-134422"
  }'

The response includes a subscriptionId you can use to check status or revoke the subscription later:

{
  "subscriptionId": "enr-33MxMppykHWC9eb3tSjWqWEK8qg",
  "status": "active",
  "reference": "CUST-134422",
  "lastActivity": null
}

Transaction Matching

Transaction Matching is an alternative to receipt subscriptions, which require a Payment Account Reference (PAR) — a unique identifier tied to a payment card. If a PAR is not available, the client can submit transaction details and Myver will search for a matching receipt. Supply as many fields as you have — the more you provide, the more accurate the match.

curl -i "https://api.prod.myver.tech/v1/transaction-match" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -d '{
        "reference": "CUST-134422",
        "transaction": {
          "lastFour": "4242",
          "approvalCode": "048236",
          "retrievalReferenceNumber": "123456789012",
          "paymentTypeLabel": "VISA"
        }
  }'

A 202 Accepted response means Myver has received the request. When a match is found, the receipt is delivered to your webhook.