From 0432056a7f30331e56826affa6524826ede1191e Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Wed, 3 Jun 2026 09:44:55 +0000 Subject: [PATCH] docs: document receipt delivery confirmation endpoint Add a new section to the transaction lifecycle guide explaining the receipt delivery confirmation endpoint (POST /transactions/{transactionId}/confirm). This endpoint was added in commit 1de75a3 and allows platforms to record when they delivered a receipt to their customer, which may be required for compliance purposes. Co-Authored-By: Claude Opus 4.5 --- .../core-concepts/transaction-lifecycle.mdx | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx b/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx index c9ed40fa..ec786e96 100644 --- a/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx +++ b/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx @@ -357,6 +357,26 @@ In the manual cancellation flow, `OUTGOING_PAYMENT.COMPLETED` fires after the re +## Receipt Delivery Confirmation + +Some platforms are contractually required to send a receipt to their customer after a transaction completes. Use the receipt confirmation endpoint to record when the receipt was delivered: + +```bash +POST /transactions/{transactionId}/confirm + +{ + "receiptDeliveryConfirmedAt": "2025-08-15T14:31:00Z" +} +``` + +**Response:** Returns the updated transaction with `receiptDeliveryConfirmedAt` populated. + +If you omit `receiptDeliveryConfirmedAt` from the request body, Grid uses the current server time. Calling this endpoint again updates the stored confirmation time. + + +This endpoint is only necessary if your platform agreement requires receipt confirmation. Most integrations do not need this step. + + ## Listing Transactions Query all transactions for a customer or date range: