Electrum Regulated Payments Partner API (26.1.1)

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.

Download OpenAPI description

elpapi-partner-redoc.json

elpapi-partner-redoc.yaml

Overview

URL

https://electrum.co.za

Electrum Support

support@electrum.co.za

Servers

Partner API sandbox

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

transactional

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

risk-assessment

Operations related to the assessment and identification of risk in transactions.

Operations

fraud-assessment

Operations related to the processing of fraud assessments for payment transactions.

Operations

account-management

Operations that involve customer account information.

Operations

sanctions-assessment

Operations related to the processing of sanctions assessment for payment transactions.

Operations

mandate-management

Operations related to the lifecycle management of direct debit mandates.

Operations

Schema

Frequency

Specifies the frequency of the payment transaction.

schemastringrequired

Value"AdHocFrequency"

Discriminator

{
  "schema": "AdHocFrequency"
}

MandateOccurrences

Defines the frequency and duration of mandate collections.

finalCollectionDatestring(date)

The date of the final collection.

firstCollectionDatestring(date)

The date of the first collection.

frequencyobject(Frequency)

Specifies the frequency of the payment transaction.

sequenceTypestring(SequenceTypeCode)required

Identifies the direct debit sequence:

FRST : First collection of a series of direct debit instructions.
RCUR : Direct debit instruction where the debtor's authorisation is used for regular direct debit transactions initiated by the creditor.
FNAL : Final collection of a series of direct debit instructions.
OOFF : Direct debit instruction where the debtor's authorisation is used to initiate one single direct debit transaction.
RPRE : Collection used to represent previously reversed or returned direct debit transactions.

Enum"FRST""RCUR""FNAL""OOFF""RPRE"

validFromstring(date)

The date from which the mandate is valid.

validTostring(date)

The date until which the mandate is valid.

{
  "finalCollectionDate": "2019-08-24",
  "firstCollectionDate": "2019-08-24",
  "frequency": {
    "dayOfMonth": 1,
    "schema": "MonthlyFrequency"
  },
  "sequenceType": "FRST",
  "validFrom": "2019-08-24",
  "validTo": "2019-08-24"
}

ExternalMandateReasonCode

schemastringrequired

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

valuestringrequired

AC01 - IncorrectAccountNumber
AC04 - ClosedAccountNumber
AC06 - BlockedAccount
AG01 - TransactionForbidden
AG02 - InvalidBankOperationCode
AM02 - NotAllowedAmount
AM03 - NotAllowedCurrency
AM05 - Duplication
BE01 - InconsistenWithEndCustomer
BE04 - MissingCreditorAddress
BE05 - UnrecognisedInitiatingParty
BE06 - UnknownEndCustomer
BE07 - MissingDebtorAddress
DT01 - InvalidDate
FF01 - InvalidFileFormat
MD01 - NoMandate
MD02 - MissingMandatoryInformationInMandate
MD07 - EndCustomerDeceased
MD08 - NoMandateServiceByAgent
MD09 - NoMandateServiceOnCustomer
MD10 - NoMandateServiceForSpecified
MD11 - UnrecognisedAgent
MD12 - NotUniqueMandateReference
MD13 - IncorrectCustomerAuthentication
MD14 - IncorrectAgent
MD15 - IncorrectCurrency
MD16 - RequestedByCustomer
MD17 - RequestedByInitiatingParty
MD18 - RequestedByInitiatingPartyAndCustomer
MD19 - MandateCancelledDueToEarlySettlement
MD20 - MandateExpired
MD21 - MandateCancelledDueToFraud
MD22 - MandateInitiationCancelled
MD23 - MandateAmendmentCancelled
MS02 - NotSpecifiedReasonCustomerGenerated
MS03 - NotSpecifiedReasonAgentGenerated
NARR - Narrative
RC01 - BankIdentifierIncorrect
RF01 - NotUniqueTransactionReference
RR01 - MissingDebtorAccountOrIdentification
RR02 - MissingDebtorNameOrAddress
RR03 - MissingCreditorNameOrAddress
RR04 - RegulatoryReason
SL01 - SpecificServiceOfferedByDebtorAgent
SL11 - CreditorNotOnWhitelistOfDebtor
SL12 - CreditorOnBlacklistOfDebtor
SL13 - MaximumNumberOfDirectDebitTransactionsExceeded
SL14 - MaximumDirectDebitTransactionAmountExceeded

Enum"AC01""AC04""AC06""AG01""AG02""AM02""AM03""AM05""BE01""BE04"

{
  "schema": "string",
  "value": "AC01"
}

operational

Operations

bulk

Operations

request-to-pay

Operations

refund

Operations

account-verification

Operations