Identifies the type of scheme specific data
Enum"DISBURSEMENT""COLLECTION"
{ "bulkFormat": "string", "bulkInformationId": "string", "bulkScheme": "DISBURSEMENT", "bulkState": "string" }
The Electrum Regulated Payments Events API is a synchronous API that describes the events emitted by the Electrum Regulated Payments platform during the course of transaction processing.
This document describes the single endpoint that you will need to implement in order to receive event notifications posted by Electrum.
As transactions are processed by Electrum, events are emitted to provide information about the status of the transactions and the operations preformed on them. These events do not affect processing, but provide information that can be used for operational support and monitoring purposes.
All events are posted to the same single URL. Event are differentiated by a unique descriptor contained in the name field of the message body. This descriptor serves to allow the receiver to determine whether the particular event is of interest.
https://example.com/path/payments/events-api/v1/
Transactions transition through different states. As each state is entered, an event is emitted. This event provides information about the state entered by the transaction. Included in this information is the message payload of the operation that triggered the state transition in the Electrum Regulated Payments. Note: The message payload attached to an event might be an internally-triggered message and not the message sent to or received from the Electrum Regulated Payments API.
The date and time at which the instruction's lifecycle state was updated The date must be formatted as defined by date-time in RFC3339
{ "instructionReq": "string", "instructionRsp": "string", "instructionType": "string", "lifecycleState": "string", "lifecycleStateUpdated": "2019-08-24T14:15:22Z" }
The version of the Electrum Regulated Payments Events API which the event format conforms to i.e. the version of this API.
The date and time at which the event was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
{ "apiVersion": "string", "class": "BULK_INDIVIDUAL_TRANSACTION_STATE", "bulkInformationId": "string", "creationDateTime": "2019-08-24T14:15:22Z", "transactionInfo": { "rawTransaction": "string", "transactionId": "string", "transactionState": "string", "transactionStateUpdated": "2019-08-24T14:15:22Z", "transactionStatusRsp": "string" } }