Transaction Events

Create a Transaction Event

POST

POST Transaction Events

/events/transaction endpoint allows you to operate on the Transaction Events entity.

Transaction events are created after the initial POST /transactions call (which creates a transaction) and are used to:

  • Update the STATE of the transaction, using the transactionState field and manage the Transaction Lifecycle
  • Update the transaction details, using the updatedTransactionAttributes field.

If you have neither of the above two use cases, you do not need to use transaction events.

Payload

Each transaction event needs three mandatory fields:

  • transactionState - STATE of the transaction -> value is set to CREATED after POST /transactions call
  • timestamp- the timestamp of when the event was created or occured in your system
  • transactionId - The ID of the transaction for which this event is generated.

In order to make individual events retrievable, you also need to pass in a unique eventId to the request body.

Request

This endpoint expects an object.
transactionState
enumRequired
Model for transaction states. E.g. Processing, Refunded, Successful etc.
timestamp
doubleRequired
Timestamp of the event
transactionId
stringRequired
Transaction ID the event pertains to
eventId
stringOptional
Unique event ID
reason
stringOptional
Reason for the event or a state change
eventDescription
stringOptional
Event description
updatedTransactionAttributes
objectOptional
Model for transaction additional payload
metaData
objectOptional
Model for device data

Response

This endpoint returns an object
eventId
string
transaction
object
executedRules
list of objects
Unique transaction identifier
hitRules
list of objects
Unique transaction identifier
riskScoreDetails
objectOptional

Errors

Built with