LIlightsparkdev
Sandbox

Simulate a card authorization expiry

Changed on

Simulate an authorization the merchant never followed through on, so the card network lets it lapse and releases the held funds. Use it to see how your integration handles a hold that quietly goes away instead of settling. The transaction must still be fully open: once any part of it has settled, it can no longer expire. Grid processes the expiry in the background. Once it lands, the transaction has status: VOIDED and Grid sends a CARD_TRANSACTION.VOIDED webhook.

Production returns 404 on this path.

post/sandbox/cards/{id}/simulate/authorization_expiry

Request

  • Base URL
    https://api.lightspark.com/grid/2025-10-13
  • URL
    https://api.lightspark.com/grid/2025-10-13/sandbox/cards/{id}/simulate/authorization_expiry
  • Auth
    HTTP basic

Path parameters

idstring required

The id of the card the expiry applies to.

Request body

cardTransactionIdstring required

The id of the CardTransaction to act against.

Example request

{
  "cardTransactionId": "Transaction:019542f5-b3e7-1d02-0000-000000000100"
}

Response

Simulation accepted. The resulting card operation is delivered asynchronously via the issuer's events webhook. Returns the issuer transaction token that correlates the simulated event.

issuerTransactionTokenstring required

The card issuer's transaction token for the simulated event. Correlates the eventual webhook-delivered card operation back to this simulate call.

Example response

{
  "issuerTransactionToken": "f3a1c2d4-5b6e-7890-abcd-ef0123456789"
}

Changes

  • d996ddfb9d2bRevision changes
    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

  • 5abf2bb56bcbRevision changes
    • warning

      added the new CORRIDOR_UNDER_MAINTENANCE enum value to the response property for the response status