/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:
transactionState
field and manage the Transaction LifecycleupdatedTransactionAttributes
field.If you have neither of the above two use cases, you do not need to use transaction events.
Each transaction event needs three mandatory fields:
transactionState
- STATE of the transaction -> value is set to CREATED
after POST /transactions
calltimestamp
- the timestamp of when the event was created or occured in your systemtransactionId
- 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.
Model for transaction states. E.g. Processing, Refunded, Successful etc.
Timestamp of the event
Transaction ID the event pertains to
Unique event ID
Reason for the event or a state change
Event description
Model for transaction additional payload
Model for device data
Unique transaction identifier
Unique transaction identifier