PAYMENT_VERIFICATION

Called when notification has been received from the payment processor that payment has been made

Submit this event using Firing an Event. Product configuration and enabled actions determine the workflow behavior. Use identifiers and snapshots from the same environment.

Request payload#

POST https://api.{ENV}.dais.com/ioi/v3/event/fire

curl --location --request POST 'https://api.{ENV}.dais.com/ioi/v3/event/fire' \
--header 'Authorization: Basic <Base64-encoded API key and secret>' \
--header 'Content-Type: application/json' \
--data-raw '{
  "lineId": "<UUID of the product ID>",
  "type": "PAYMENT_VERIFICATION",
  "payload": {
    "clientId": "<UUID of the client ID>",
    "paymentSessionId": "<UUID of the payment session ID>"
  }
}'

{
  "lineId": "<UUID of the product ID>",
  "type": "PAYMENT_VERIFICATION",
  "payload": {
    "clientId": "<UUID of the client ID>",
    "paymentSessionId": "<UUID of the payment session ID>"
  }
}

Request Fields#

See the shared event envelope. Set type to PAYMENT_VERIFICATION and provide the payload below.

Payload Fields#

Property	Required	Description
`clientId`	Yes	Client identifier, used in activity logging.
`paymentSessionId`	Yes	Session identifier to verify with the Payments service.

Response#

This example illustrates the common trigger response structure. Action counts and metadata depend on the actions that run; action-specific result fields are described where applicable.

{
  "triggerRequestId": "<UUID of the trigger request ID>",
  "executedActionCount": 0,
  "expectedResponseCount": 0,
  "metadata": {}
}

The built-in action returns the updated payload under metadata.PAYMENT_VERIFICATION, including paymentVerified, amount, paymentIdentifier, and paymentProcessor. A verified result can represent a pending or reserved payment; it does not by itself establish final settlement.

Response Fields#

Property	Description
`triggerRequestId`	UUID identifying this trigger execution.
`executedActionCount`	Number of actions reported as executed.
`expectedResponseCount`	Number of expected action responses.
`metadata`	Action-specific results; may be empty.

See Firing an Event for execution modes and response handling.