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 1/3] 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 c9ed40fa3..ec786e96c 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: From 68764f57fa288e2b0ffdb732a9229305fa823b5b Mon Sep 17 00:00:00 2001 From: Peng Ying Date: Wed, 10 Jun 2026 10:10:15 -0700 Subject: [PATCH 2/3] Update transaction-lifecycle.mdx --- .../core-concepts/transaction-lifecycle.mdx | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx b/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx index ec786e96c..f9c6488d8 100644 --- a/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx +++ b/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx @@ -362,14 +362,10 @@ In the manual cancellation flow, `OUTGOING_PAYMENT.COMPLETED` fires after the re 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. +curl -X POST "https://api.example.com/transactions/{transactionId}/confirm" \ + -H "Content-Type: application/json" \ + -H "Authorization: Bearer YOUR_API_KEY" \ + -d '{"receiptDeliveryConfirmedAt": "2025-08-15T14:31:00Z"}' If you omit `receiptDeliveryConfirmedAt` from the request body, Grid uses the current server time. Calling this endpoint again updates the stored confirmation time. From d1d5b0b0208c9a0339665de4148a083a80bb5e75 Mon Sep 17 00:00:00 2001 From: Bolt Agent Date: Thu, 30 Jul 2026 16:31:32 +0000 Subject: [PATCH 3/3] docs: close bash fence in receipt delivery confirmation section Close the unclosed bash fence so the following prose and Info callout render as documentation instead of raw code, and align the curl example with the versioned api.lightspark.com base URL and BasicAuth used elsewhere in this guide. Co-Authored-By: jklein24 --- .../core-concepts/transaction-lifecycle.mdx | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx b/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx index f9c6488d8..5d981a6aa 100644 --- a/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx +++ b/mintlify/platform-overview/core-concepts/transaction-lifecycle.mdx @@ -362,10 +362,21 @@ In the manual cancellation flow, `OUTGOING_PAYMENT.COMPLETED` fires after the re 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 -curl -X POST "https://api.example.com/transactions/{transactionId}/confirm" \ +curl -X POST https://api.lightspark.com/grid/2025-10-13/transactions/Transaction:019542f5-b3e7-1d02-0000-000000000030/confirm \ + -u "$GRID_CLIENT_ID:$GRID_CLIENT_SECRET" \ -H "Content-Type: application/json" \ - -H "Authorization: Bearer YOUR_API_KEY" \ -d '{"receiptDeliveryConfirmedAt": "2025-08-15T14:31:00Z"}' +``` + +**Response:** the updated transaction, with `receiptDeliveryConfirmedAt` populated: + +```json +{ + "id": "Transaction:019542f5-b3e7-1d02-0000-000000000030", + "status": "COMPLETED", + "receiptDeliveryConfirmedAt": "2025-08-15T14:31:00Z" +} +``` If you omit `receiptDeliveryConfirmedAt` from the request body, Grid uses the current server time. Calling this endpoint again updates the stored confirmation time.