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

InvestigationStatusConfirmation

Specifies the status of the investigation, in a coded form

confirmationCodestring(InvestigationExecutionCode)required

ACDA AcceptedDebitAuthorisation - Used when a creditor accepts the debit authorisation.
ACNR AcceptedClaimNonReceipt - The claim for non-receipt of a payment instruction is accepted.
ACVA AcceptedValueDateAdjustment - The claim for value date correction is accepted.
BIAS BatchInstructionAlreadySettled - Process a cancellation request but batch already settled.
CHRG ChargesDetailsProvided - Further charges details are provided to resolve the case.
CNCL CancelledAsPerRequest - Used when a requested cancellation is successful.
CONF ConfirmationOfPayment - Used when a payment has been checked and was correctly executed without any intervention.
CVAA CorrectValueDateAlreadyApplied - The original value date was correct.
CWFW CancellationWillFollow - Used when a payment will be cancelled to solve an investigation case.
FTNA CancellationRequestForwardedToTheNextAgent - "The cancellation request has been forwarded to the next agent for execution. This code should only be utilised where a Case Id is not present."
ICOV CoverInitiated - Used when a transfer of funds has been initiated (a cover payment) to resolve a case.
IDNE InstructionDoesNotExist - Process a Batch Cancellation "using an incorrect batch sequence number”.
IDUP InstructionIsDuplicate - Used when the requested check for a possible duplicate instruction is confirmed.
INFO AdditionalInformationSent - Used when additional information has been sent to the beneficiary of a payment.
IPAY PaymentInitiated - Used when the result of an investigation is, or will be, the initiation of a payment instruction.
IPYI PaymentInstructionInitiated - Used when a payment instruction (eg. MT103) has been initiated to resolve a case.
IVCR InvalidCancellationRequest - Process a cancellation request with incorrect reference to original batch.
MCOV CoverModified - Used when a transfer of funds has been modified (a cover payment) to resolve a case.
MODI ModifiedAsPerRequest - Used when a requested modification is successful.
MWFW ModificationWillFollow - Used when the payment will be modified to solve an investigation case.
NINF NoInformationAvailable - Used when no additional information is available.
PDCR PendingCancellationRequest - Used when a requested cancellation is pending.
PDNG Pending - Used to inform that a response to an investigation is pending.
PECR PartiallyExecutedCancellationRequest - Used when a requested cancellation has been partially executed.
PURP PurposeDetailsProvided - Further purpose details are provided to resolve the case.
RJCR RejectedCancellationRequest - Used when a requested cancellation has been rejected.
RJNR RejectedClaimNonReceipt - The claim for non-receipt of a payment instruction is rejected.
RJVA RejectedValueDateAdjustment - The claim for value date correction is rejected.
SMTC StatementEntryCorrect - Used when the entry in the statement is correct.
SMTI StatementEntryIncorrect - Used when the entry in the statement is incorrect and further information is provided with the resolution.
UWFW UnableToApplyWillFollow - Used when sender wants to respond to an assignment with an Unable To Apply workflow.

Enum"ACDA""ACNR""ACVA""BIAS""CHRG""CNCL""CONF""CVAA""CWFW""FTNA"

statusTypestringrequired

Value"CONFIRMATION"

{
  "confirmationCode": "ACDA",
  "statusType": "CONFIRMATION"
}

InvestigationStatusDuplicateOf

Indicates a duplicated case

duplicateOfobject(Case6)required

duplicateOf.creatorany(PartyInstitutionChoice)

duplicateOf.identificationstring<= 35 characters

duplicateOf.reopenCaseIndicationboolean

Indicates whether or not the case was previously closed and is now re-opened

statusTypestringrequired

Value"DUPLICATE_OF"

{
  "duplicateOf": {
    "creator": { … },
    "identification": "string",
    "reopenCaseIndication": true
  },
  "statusType": "DUPLICATE_OF"
}

ExternalPaymentModificationRejectionCode

schemastring

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

valuestring

UM01 UnableToModifyRelatedReference - Related transaction reference cannot be modified.
UM02 UnableToModifyPaymentServiceLevel - Service level element of payment type cannot be modified(former UnableToModifyBankOperationCode).
UM03 UnableToModifyCategoryPurpose - Category purpose element of payment type cannot be modified (former UnableToModifyInstructionCode).
UM04 UnableToModifyRequestedExecutionDate - RequestedExecutionDate cannot be modified.
UM05 UnableToModifyInterbankSettlementDate - InterbankSettlementDate cannot be modified (former UnableToModifyValueDate).
UM06 UnableToModifyInterbankSettlementAccount - SettlementAccount cannot be modified (former UnableToModifyInterbankSettlementAccount).
UM07 UnableToModifyDebtor - Debtor cannot be modified.
UM08 UnableToModifyDebtorAccount - DebtorAccount cannot be modified.
UM09 UnableToModifyInstructedReimbursementAgent - InstructedReimbursementAgent cannot be modified (former UnableToModifyReceiverCorrespondent).
UM10 UnableToModifyThirdReimbursementAgent - ThirdReimbursementAgent cannot be modified (former UnableToModifyThirdReimbursementInstitution).
UM11 UnableToModifyPaymentClearingChannel - Clearing Channel element of payment type cannot be modified (former UnableToModifyPaymentScheme)
UM12 UnableToModifyCreditorAgentAccount - Creditor agent account cannot be modified (former UnableToModifyAccountOfBeneficiaryInstitution)
UM13 UnableToModifyCreditor - Creditor cannot be modified.
UM14 UnableToModifyCreditorAccount - Creditor account cannot be modified.
UM15 UnableToModifyRemittanceInformation - Remittance information cannot be modified.
UM16 UnableToModifyPaymentPurpose - PaymentPurpose cannot be modified.
UM17 UnableToModifyChargeBearer - Charge bearer cannot be modified (former UnableToModifyDetailsOfCharges).
UM18 UnableToModifyInstructionForNextAgent - Instruction for next agent cannot be modified (former UnableToModifySenderToReceiver).
UM19 UnableToModifyInstructionForCreditorAgent - Instruction for creditor agent cannot be modified. (former UnableToModifyInstructionForFinalAgent).
UM20 InstructionCancelledSubmitNewInstruction - Used to inform of cancellation and request a new payment instruction. This should only be used if an agent does not want to modify a pending payment.
UM21 UnableToModifySubmitCancellation - Modification is not possible and the cancellation is requested.
UM22 UnableToModifyDebtorAgentAccount - Debtor agent account cannot be modified (applicable for direct debits).
UM23 UnableToModifyInterbankSettlementAmount - Interbank settlement amount cannot be modified.
UM24 UnableToModifyInstructionForDebtorAgent - Instruction for debtor agent cannot be modified (applicable for direct debits)
UM25 UnableToModifyRequestedCollectionDate - Requested collection date cannot be modified (applicable for direct debits)
UM26 UnableToModifyPaymentType - Payment type cannot be modified.
UM27 UnableToModifyInstructedAmount - Instructed or equivalent amount cannot be modified.
UM28 UnableToModifyPriority - Priority of payment message cannot be modified.

Enum"UM01""UM02""UM03""UM04""UM05""UM06""UM07""UM08""UM09""UM10"

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

operational

Operations

bulk

Operations

request-to-pay

Operations

refund

Operations

account-verification

Operations