Electrum Regulated Payments Events API (17.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
Mock server

https://docs.electrumsoftware.com/_mock/openapi/elpapi/elpapi-events/

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

ChargeBearer

  • DEBT (BorneByDebtor): All transaction charges are to be borne by the debtor
  • CRED (BorneByCreditor): All transaction charges are to be borne by the creditor
  • SHAR (Shared): In a credit transfer context, means that transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. In a direct debit context, means that transaction charges on the sender side are to be borne by the creditor, transaction charges on the receiver side are to be borne by the debtor.
  • SLEV (FollowingServiceLevel): Charges are to be applied following the rules agreed in the service level and/or scheme
string(ChargeBearer)
  • DEBT (BorneByDebtor): All transaction charges are to be borne by the debtor
  • CRED (BorneByCreditor): All transaction charges are to be borne by the creditor
  • SHAR (Shared): In a credit transfer context, means that transaction charges on the sender side are to be borne by the debtor, transaction charges on the receiver side are to be borne by the creditor. In a direct debit context, means that transaction charges on the sender side are to be borne by the creditor, transaction charges on the receiver side are to be borne by the debtor.
  • SLEV (FollowingServiceLevel): Charges are to be applied following the rules agreed in the service level and/or scheme
Enum"DEBT""CRED""SHAR""SLEV"
"DEBT"

ChargeTypeCode

schemastringrequired

Identifies the value as being a pre-defined code. Always CODE.

valuestringrequired
  • BRKF (BrokerageFee): Fee paid to a broker for services provided.
  • BTCH (Batch): Fee paid for processing a batch of transactions.
  • COMM (Commission): Fee paid for services provided.
  • SUMM (Summation): Summation of individual fees.
  • AMND (Amendment): Payment order was changed based on request to do so from the (original) sending bank or as a result of receiving amended information from the (original) sending bank.
  • CFEE (CancellationFee): Used when fees are assessed for cancellation of a payment.
  • CLEF (ClearingFee): Used when fees are assessed for standard processing of financial institution type transfers.
  • INVS (Investigation): Charges related to the processing of an investigation case/inquiry.
  • INTE (Interest): Interest related charges.
  • NSTP (NonSTPCharges): Charge for a payment that required an intervention during processing.
  • DEBT (BorneByDebtor): Claim is being submitted in response to receiving a customer credit transfer with DEBT in Charge Bearer code.
  • TELE (TelecommunicationCharges): Charges relating to the most appropriate and efficient means of telecommunications available, for example, SWIFT, telex, telephone, facsimile, as determined by the party executing the payment instruction.
  • ACCM (AccMaintenanceFee): Account maintenance fee.
  • RECH (ReportingCharges): Charge for a reporting message (camt.05X).
Enum"BRKF""BTCH""COMM""SUMM""AMND""CFEE""CLEF""INVS""INTE""NSTP"
{ "schema": "string", "value": "BRKF" }

ChargeType

schemastringrequired

Identifies the value as being a pre-defined code. Always CODE.

Discriminator
valuestringrequired
  • BRKF (BrokerageFee): Fee paid to a broker for services provided.
  • BTCH (Batch): Fee paid for processing a batch of transactions.
  • COMM (Commission): Fee paid for services provided.
  • SUMM (Summation): Summation of individual fees.
  • AMND (Amendment): Payment order was changed based on request to do so from the (original) sending bank or as a result of receiving amended information from the (original) sending bank.
  • CFEE (CancellationFee): Used when fees are assessed for cancellation of a payment.
  • CLEF (ClearingFee): Used when fees are assessed for standard processing of financial institution type transfers.
  • INVS (Investigation): Charges related to the processing of an investigation case/inquiry.
  • INTE (Interest): Interest related charges.
  • NSTP (NonSTPCharges): Charge for a payment that required an intervention during processing.
  • DEBT (BorneByDebtor): Claim is being submitted in response to receiving a customer credit transfer with DEBT in Charge Bearer code.
  • TELE (TelecommunicationCharges): Charges relating to the most appropriate and efficient means of telecommunications available, for example, SWIFT, telex, telephone, facsimile, as determined by the party executing the payment instruction.
  • ACCM (AccMaintenanceFee): Account maintenance fee.
  • RECH (ReportingCharges): Charge for a reporting message (camt.05X).
Enum"BRKF""BTCH""COMM""SUMM""AMND""CFEE""CLEF""INVS""INTE""NSTP"
{ "schema": "CODE", "value": "BRKF" }