The Electrum Regulated Payments API is an asynchronous API that allows partners to participate in various nationally regulated payment schemes.
As the Regulated Payments API is asynchronous, partners have a choice of how to integrate with Electrum:
Webhooks: Electrum will send events to the partner containing inbound payments to action, or responses to outbound payment requests. Webhooks are defined in the Electrum Regulated Payments Partner API.
Partner API: Electrum will call operations exposed by the partner containing inbound payments to action, or responses to outbound payment requests. The operations are defined in this document.
Receiving transactional events via webhooks or API are equivalent, except that it may be more familiar or convenient to implement one style or the other.
This document describes the operations a partner must implement for Electrum to consume in order to complete the integration with the Electrum Regulated Payments API.
Operations that participate in transaction processing, which may or may not have financial impact.
Operations
financial
Operations that participate in transaction processing and have financial impact.
Operations
credit-transfer
Operations related to credit transfer transactions.
Operations
direct-debit
Operations related to direct debit transactions.
Operations
payment-return
Operations related to payment returns.
Operations
identifier-determination
Operations used to retrieve additional information related to an identifier
Operations
funds-management
Operations related to the management of funds, including reservations, postings, and voiding of reservations.
Operations
Schema
ReservationType
schemastringrequired
Identifies the value as being a pre-defined code. Always CODE.
Discriminator
valuestringrequired
BLKD - Blocked - Amount blocked or frozen due to external circumstances such as a court order, death of beneficiary or account owner, or bankruptcy.
CARE - CashReservation - Amount set aside by a participant to reserve liquidity from its own account, exclusively or executing cash withdrawals.
HPAR - HighlyUrgentPaymentReservation - Amount set aside by a participant to reserve liquidity from its own account, exclusively for executing highly urgent payments.
NSSR - NetSSSReservation - Amount set aside by a participant to reserve liquidity from its own account, exclusively for the settlement of the multilateral cash balance stemming from the Net Security Settlement System.
THRE - ThresholdForInvestment - Amount above which funds will be destined for investment.
UPAR - UrgentPaymentReservation - Amount set aside by a participant to reserve liquidity from its own account, exclusively for executing critical payments called urgent payments.
Enum"BLKD""CARE""HPAR""NSSR""THRE""UPAR"
{
"schema": "CODE",
"value": "BLKD"
}
ReservationRequest
A model containing the necessary information to perform a reservation of funds on an account.
A reference used to unambiguously identify the message between the sending and receiving party. Take note that this uniquely identifies a single message in a potentially multi-message exchange to complete a payment.
supplementaryDataobject
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
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. Note: this is distinct from the UETR.
Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the instruction. The instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.
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.
transactionIdentifiers.uetrstring(UUID)required
Universally unique identifier to provide an end-to-end reference of a payment transaction. This identifier remains the same for all messages related to the same transaction.
Name of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account.
A valid, active currency code as defined in ISO 4217 indicating the currency of the amount.
amount.valuenumber(double)>= 0required
The payment amount in the denomination of the indicated currency, in the format '. with the number of minor units (fractional digits) compliant with the number of decimal places published in ISO 4217.
Currency Code
Example
Valid
Notes
USD
10.0
✓
Represents 10 USD and no cents.
USD
10.00
✓
USD
10.001
✗
US dollar does not support three decimal places.
JPY
10.0
✓
Represents 10 Japanese Yen.
JPY
10.1
✗
Japanese Yen does not support decimal places.
initiationSourcestring
Free text field used to inform the core banking system of which system is initiating the reservation.
referencestring<= 35 characters
An explanation of the transaction, e.g. to be printed on the account holder's statement.
A reference used to unambiguously identify the message between the sending and receiving party. Take note that this uniquely identifies a single message in a potentially multi-message exchange to complete a payment.
supplementaryDataobject
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
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. Note: this is distinct from the UETR.
Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the instruction. The instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.
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.
transactionIdentifiers.uetrstring(UUID)required
Universally unique identifier to provide an end-to-end reference of a payment transaction. This identifier remains the same for all messages related to the same transaction.
Name of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account.
A valid, active currency code as defined in ISO 4217 indicating the currency of the amount.
amount.valuenumber(double)>= 0required
The payment amount in the denomination of the indicated currency, in the format '. with the number of minor units (fractional digits) compliant with the number of decimal places published in ISO 4217.
Currency Code
Example
Valid
Notes
USD
10.0
✓
Represents 10 USD and no cents.
USD
10.00
✓
USD
10.001
✗
US dollar does not support three decimal places.
JPY
10.0
✓
Represents 10 Japanese Yen.
JPY
10.1
✗
Japanese Yen does not support decimal places.
initiationSourcestring
Free text field used to inform the core banking system of which system is initiating the void.
paymentUetrstring(UUID)required
UUID which links the void to a payment instruction, and its initial reservation.