PAYMENT_TRANSACTION_RECORD

Record a payment only, with no system validation of transaction with Payment provider.

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 '{
  "type": "PAYMENT_TRANSACTION_RECORD",
  "payload": {
    "policyId": "<UUID of the policy ID>",
    "clientId": "<UUID of the client ID>",
    "quoteId": "<UUID of the quote request ID>",
    "documents": [],
    "amount": 525.0,
    "receivedDate": "2026-03-01T14:25:29-05:00",
    "paymentType": "MANUAL_RECORD",
    "paymentSpec": {
      "label": "<Label>",
      "description": "<Description>"
    }
  }
}'

{
  "type": "PAYMENT_TRANSACTION_RECORD",
  "payload": {
    "policyId": "<UUID of the policy ID>",
    "clientId": "<UUID of the client ID>",
    "quoteId": "<UUID of the quote request ID>",
    "documents": [],
    "amount": 525.0,
    "receivedDate": "2026-03-01T14:25:29-05:00",
    "paymentType": "MANUAL_RECORD",
    "paymentSpec": {
      "label": "<Label>",
      "description": "<Description>"
    }
  }
}

Request Fields#

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

Payload Fields#

Required fields include the inputs used by this event's built-in action. Configured actions can require additional data.

Property	Required	Description
`policyId`	Yes	UUID of the policy.
`clientId`	No	UUID of the client.
`quoteId`	No	UUID of the quote.
`documents`	No	List of documents related to the event.
`amount`	Yes	Decimal amount of the payment.
`receivedDate`	Yes	Timestamp with timezone offset representing when the payment was received.
`paymentType`	Yes	Must be `MANUAL_RECORD` or `CREDIT_CARD`, see below for details.
`paymentSpec`	No	Additional payment specification map.

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": {}
}

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.