Electrum Regulated Payments Events API (18.1.0)

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.

Download OpenAPI description
Overview
Languages
Servers
Payments API sandbox

https://example.com/path/payments/events-api/v1/

state

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.

Operations

Schema

EventEsmState

financialTransactionStatestringrequired

The state of the financial transaction for the given transaction.

Enum"IN_PROGRESS""ACTIONED""UNPAID""ERROR""UNMATCHED"
transactionStatestringrequired

The state of the given transaction.

Enum"RECEIVE_PENDING""RECEIVED""RECEIVE_ERROR""CANCELLED""SEND_PENDING""SENT""SEND_ERROR""ON_HOLD"
{ "financialTransactionState": "IN_PROGRESS", "transactionState": "RECEIVE_PENDING" }

EventEsmTransactionInfo

directionstringrequired

Indicates the direction of the payment, from the perspective of Electrum and the Partner.

Enum"INBOUND""OUTBOUND""ON_US"
paymentTypestringrequired

Enumerates the specific transaction processing event being emitted.

Enum"CREDIT""DEBIT"
recordTypestringrequired
Enum"PAYMENT""UNPAID_INPUT""UNPAID_OUTPUT""RECALL_OUTPUT""SEC_REQUEST""SEC_RESPONSE""SEC_UNPAID_INPUT""HOMED_BACK"
returnTypestring

Indicates the cause of an unpaid/payment return.

Enum"DISPUTE""UNPAID""HOME_BACK""SEC_SUCCESSFUL""RECALL_RESULT"
subServicestringrequired
Enum"SAME_DAY""ONE_DAY""TWO_DAY""RECALLS""SYSTEM_ERROR_CORRECTION""SYSTEM_ERROR_CORRECTION_RESPONSE"
{ "direction": "INBOUND", "paymentType": "CREDIT", "recordType": "PAYMENT", "returnType": "DISPUTE", "subService": "SAME_DAY" }

EsmStateEvent

An event that indicates a state change of the ESM for a given transaction. An event contains information An event that indicates a state change of the ESM for a given transaction. An event contains information regarding the ESM's view of a given transaction as the state of the transaction changes.

apiVersionstringrequired

The version of the Electrum Regulated Payments Events API which the event format conforms to i.e. the version of this API.

classstringrequired

The class of the event.

Discriminator
bulkInformationIdstring(UUID)required

A UUID to identify the bulk

creationDateTimestring(date-time)required

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

transactionInfoobject(BulkEventTransactionInfo)
{ "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" } }