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
elpapi-events.json
elpapi-events.yaml
Overview
URL

https://electrum.co.za

Electrum Support

support@electrum.co.za

License

proprietary

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

UnpaidOutputRecord

effectiveActionDatestring(date)required

The date at which the transaction should take effect. The date must be formatted as defined by date-time in RFC3339

filler1integer
newSequenceNumberintegerrequired
originalAccountTypeintegerrequired
originalActionDatestring(date)required

The date at which the transaction should take effect. The date must be formatted as defined by date-time in RFC3339

originalAmountinteger
originalEntryClassintegerrequired
originalHomingAccountNamestringrequired
originalHomingInstitutioninteger
originalSequenceNumberintegerrequired
originalTaxCodeinteger
originalUserReferencestringrequired
reasonCodestring(ReasonCode)required
Enum"NOT_PROVIDED_FOR""DEBITS_OR_CREDITS_NOT_ALLOWED_TO_ACCOUNT""PAYMENT_STOPPED_BY_ACCOUNT_HOLDER""ACCOUNT_FROZEN""ACCOUNT_IN_SEQUESTRATION""ACCOUNT_IN_LIQUIDATION""ACCOUNT_CLOSED""ACCOUNT_TRANSFERRED_WITHIN_BANKING_GROUP""ACCOUNT_TRANSFERRED_TO_OTHER_BANKING_GROUP""ACCOUNT_HOLDER_DECEASED"
recordIdentifierstring(RecordIdentifier)required
Enum"CREDIT""STOP_ORDER_CREDIT""CONSOLIDATED_UNPAID_CREDIT""UNPAID_CREDIT""CREDIT_RECALL""CREDIT_SEC_REQUEST""CREDIT_SEC_RESPONSE""DEBIT""CONSOLIDATED_UNPAID_DEBIT""UNPAID_DEBIT"
filler2string
filler3string
filler4string
filler5string
newAccountstring
newAccountTypestring
newBranchstring
originalHomingAccountstringrequired
originalHomingBranchstringrequired
originalUserAccountstringrequired
originalUserBranchstringrequired
schemastringrequired
Value"UnpaidOutputRecord"
userCodestringrequired
{
  "effectiveActionDate": "2019-08-24",
  "filler1": 0,
  "newSequenceNumber": 0,
  "originalAccountType": 0,
  "originalActionDate": "2019-08-24",
  "originalAmount": 0,
  "originalEntryClass": 0,
  "originalHomingAccountName": "string",
  "originalHomingInstitution": 0,
  "originalSequenceNumber": 0,
  "originalTaxCode": 0,
  "originalUserReference": "string",
  "reasonCode": "NOT_PROVIDED_FOR",
  "recordIdentifier": "CREDIT",
  "filler2": "string",
  "filler3": "string",
  "filler4": "string",
  "filler5": "string",
  "newAccount": "string",
  "newAccountType": "string",
  "newBranch": "string",
  "originalHomingAccount": "string",
  "originalHomingBranch": "string",
  "originalUserAccount": "string",
  "originalUserBranch": "string",
  "schema": "UnpaidOutputRecord",
  "userCode": "string"
}

EventEsmPayload

actionDatestring(date)required
amountinteger(int64)required
homingAccountstringrequired
homingAccountNamestringrequired
homingBranchstringrequired
recordIdentifierstring(RecordIdentifier)required
Enum"CREDIT""STOP_ORDER_CREDIT""CONSOLIDATED_UNPAID_CREDIT""UNPAID_CREDIT""CREDIT_RECALL""CREDIT_SEC_REQUEST""CREDIT_SEC_RESPONSE""DEBIT""CONSOLIDATED_UNPAID_DEBIT""UNPAID_DEBIT"
sequenceNumberintegerrequired
userAccountstringrequired
userBranchstringrequired
userCodestringrequired
userReferencestringrequired
accountTypestring(BankServAccountType)required
Enum"OTHER""CURRENT""SAVINGS""TRANSMISSION""BOND""SUBSCRIPTION_SHARE"
entryClassstring(EntryClass)required
Enum"CONTRAS""DEBIT_INSURANCE_PREMIUM""DEBIT_PENSION_FUND_CONTRIBUTION""DEBIT_MEDICAL_AID_FUND_CONTRIBUTION""DEBIT_UNIT_TRUST_PURCHASE""DEBIT_CHARITABLE_OR_RELIGIOUS_CONTRIBUTIONS""DEBIT_HP_REPAYMENT""DEBIT_ACCOUNT_REPAYMENT""DEBIT_LOAN_REPAYMENT_OTHER_THAN_MORTGAGE""DEBIT_RENTAL_LEASE_OTHER_THAN_PROPERTY"
filler1stringrequired
filler2stringrequired
filler3stringrequired
filler4stringrequired
homingInstitutionstringrequired
nonStandardHomingAccountstringrequired
schemastringrequired
Value"PaymentRecord"
Discriminator
taxCodestringrequired
{
  "actionDate": "2019-08-24",
  "amount": 0,
  "homingAccount": "string",
  "homingAccountName": "string",
  "homingBranch": "string",
  "recordIdentifier": "CREDIT",
  "sequenceNumber": 0,
  "userAccount": "string",
  "userBranch": "string",
  "userCode": "string",
  "userReference": "string",
  "accountType": "OTHER",
  "entryClass": "CONTRAS",
  "filler1": "string",
  "filler2": "string",
  "filler3": "string",
  "filler4": "string",
  "homingInstitution": "string",
  "nonStandardHomingAccount": "string",
  "schema": "PaymentRecord",
  "taxCode": "string"
}

EventEsmIdentifiers

Holds a series of identifiers to identify the transaction or an individual message that is part of a transaction.

endToEndIdentificationstring<= 35 charactersrequired

Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.

matchingKeystring<= 64 characters

A unique identifier that is used to identify an EFT record. This field is computed using the fields in the EFT record.

transactionIdentificationstring<= 35 charactersrequired

Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to make sure that the transaction identification is unique for a pre- agreed period.

uetrstring(UUID)required

Universally unique identifier to provide an end-to-end reference. This identifier remains the same for all messages related to the same transaction.

{
  "endToEndIdentification": "string",
  "matchingKey": "string",
  "transactionIdentification": "string",
  "uetr": "string"
}
Copyright 2025 | Electrum Payments (Pty) Ltd