URL
Electrum Support
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:
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.
https://example.com/path/payments/partner-api/v1/
This operation is asynchronous. The partner responds by calling the inboundMandateAcceptanceReport operation.
Receives a mandate initiation request from Electrum when a creditor initiates a new direct debit mandate. The partner should authenticate the mandate with the debtor, validate the request, and respond with the debtor's acceptance or rejection decision.
| Scheme | Applicable |
|---|---|
| ZA_AC | ✓ |
A value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Core mandate data structure containing all the details of a direct debit mandate.
Identifies the specific mechanism or channel that the Paying Bank (Debtor Bank) uses to communicate with the Payer (Debtor) to obtain their authorisation for a mandate. This field may be missing on mandate initiation/amendment and should be populated by the debtor bank upon acceptance of the mandate
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
A code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
The identification of a party, either a person or an organisation.
The name by which this party is commonly known in day to day use. For example, a shortening of their legal name or a nickname that they commonly use. This is "non-official". However, it is acceptable for this field to be set to the same as legalName.
Representation of an account for payment purposes. Note that at least one of identification or proxy is expected to be present.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
A code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
The identification of a party, either a person or an organisation.
The name by which this party is commonly known in day to day use. For example, a shortening of their legal name or a nickname that they commonly use. This is "non-official". However, it is acceptable for this field to be set to the same as legalName.
Representation of an account for payment purposes. Note that at least one of identification or proxy is expected to be present.
A code allocated to a financial or non-financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Banking - Banking telecommunication messages - Business identifier code (BIC)
An organisation identified by a code allocated to a party as described in ISO 17442 Financial Services - Legal Entity Identifier (LEI).
Name by which an institution is known and which is usually used to identify that institution
A unique identifier assigned to a company or organisation by a duly appointed authority within a country.
Unique identification of the mandate, as assigned by the creditor. This field is used strictly by the Creditor for their own internal referencing and may be used to link collections to their related mandate. This is required for mandate initiations and cancellations.
Reference assigned to the mandate by the mandate management application. This is distinct from mandateIdentification (creditor's ID) and ZaMandatePaymentSchemeSupplementaryData.debtorBankMandateReference (debtor bank's reference).
Unique identification of the mandate request, as assigned by the creditor to the debtor when the underlying contract is concluded between the two parties. This field represents the Contract Reference Number. It appears on the debtor's bank statement to help them identify the deductions. This is required for mandate initiations and mandate cancellations.
Defines the frequency and duration of mandate collections.
Specifies the reason for a mandate action (amendment, cancellation, rejection).
Provides information to identify the underlying documents associated with the mandate
Indicates whether the mandate permits tracking for future collection instructions. Its exact meaning and relevance depend strictly on the mandate-management operation being performed:
1. Mandate Initiation & Amendment Requests
true) or revoked (false) for future collections against this mandate.2. Mandate Cancellation Requests
true: Instructs the clearing house to immediately cancel any active tracking records currently in the tracking queue for this mandate.false: Instructs the clearing house NOT to cancel records in tracking, allowing them to finish their tracking cycle despite the mandate being cancelled.3. Mandate Acceptance Reports
true or false) that was successfully saved to the Debtor Bank's Mandate Register.4. Mandate Suspensions & Information Requests
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Designates which scheme a mandate operation is associated with and describes scheme-specific information for the mandate operation where relevant.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.South Africa specific supplementary data fields. These fields supplement the core mandate structure with local requirements.
Indicates the delivery and authentication mechanism of the mandate transaction.
In the ZA_AC scheme, this field dictates the specific Transaction Type (TT) processing rules that will be applied:
REAL_TIME: Maps to TT1 (non-card). The mandate request is routed over the real-time interbank switch without an upfront authentication key. Note: The actual Payer authorisation might be immediate (e.g., 120-second USSD timeout) or delayed (until the end of the day), but the routing type remains REAL_TIME.PREAUTH: Maps to TT3 (Card Present). Indicates the Payer has already been authenticated via a prior card-and-PIN transaction at the point of interaction. Mandates using this type must include the resulting Message Authentication Code (MAC) in the request payload.BATCH: Maps to TT2. The mandate request is submitted via delayed bulk file processing.NOT_APPLICABLE: Debtor authentication is not required for this action (e.g. MandateInformationRequest).The Payer's preferred recurring day for collection from their bank account.
In the ZA_AC scheme, the Collection Day is a rigid, legally binding clearing rule that is strictly evaluated relative to the mandate's Frequency. The interpretation of this integer changes based on the frequency type:
Monthly, Quarterly, Bi-annually, Annually, Once-off: Values 1 to 30 represent the exact calendar day of the month. 99 strictly represents the "Last Day" of the month (e.g., automatically adjusting for February 28th/29th). Note: 31 is not a valid input.Weekly: Values 1 to 7 represent the day of the week (1 = Monday, 7 = Sunday).Fortnightly: Values 1 to 14 represent the day within the two-week cycle (1 to 7 for week one; 8 to 14 for week two).Monthly by Rule: Values map to specific occurrences (e.g., 1 = Last Monday, 7 = First Monday, 14 = 2nd Last Day).Interbank Validation Rules: The Debtor Bank is required to store this exact day in their Mandate Register. If the mandate's dateAdjustmentRule is set to 'N' (No), the Debtor Bank will strictly validate incoming collections against this day. If a collection's Action Date does not exactly match this collectionDay (or the immediately following Processing Day), the Debtor Bank will trigger an upfront rejection.
Note: According to clearing rules, Debtor Banks are only required to enforce this strict date validation on Weekly and Monthly frequencies.
This dictates strict interbank validation rules for how collection amounts are calculated, capped, and adjusted over the life of the mandate.
The rules for each type are:
FIXED: Used for contracts where an upfront, calculated Instalment Amount is the basis for normal collections. Regular collections are strictly validated and cannot exceed this Instalment Amount. The Adjustment Category for a fixed mandate must strictly be 'NEVR' (Never).VARIABLE: Used for contracts where an upfront Instalment Amount is calculated but can be amended by the Creditor based on pre-agreed variables, such as annual increases or interest rate changes. Regular collections cannot exceed the currently active Instalment Amount.USAGE_BASED: Used for contracts where the collection amount fluctuates depending on the Payer's usage of a product or service during the payment cycle. Unlike Fixed and Variable mandates, the regular Instalment Amount is optional, and interbank validation is instead performed strictly against a mandatory Maximum Collection Amount.The Mandate Reference Number (MRN) assigned by the debtor bank upon mandate acceptance. This is the official, unique industry-wide identification number for the mandate that is unique for the mandate's entire lifecycle (including time in archives).
It is returned in the acceptance report and must be included in subsequent mandate amendment, and suspension requests.
Not to be confused with mandateIdentification (creditor's internal ID), mandateRequestTransactionIdentifier (MRTI), or mandateReference (mandate management app reference).
Structure (22 characters):
YYYYMMDD.Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
https://example.com/path/payments/partner-api/v1/mandates/inbound/initiation
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/inbound/initiation \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "MandateInitiationRequest",
"messageIdentifiers": {
"messageIdentification": "100/MANOT/00210007/20190305/000511",
"creationDateTime": "2019-03-05T10:04:44Z"
},
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"mandateRequestTransactionIdentifier": "00072019-03-05000000086",
"authenticationType": "REAL_TIME",
"requestTransmissionNumber": 1,
"collectionDay": 29,
"debitValueType": "VARIABLE"
}
},
"initiatingParty": {
"legalName": "EXAMPLE LOANS"
},
"mandate": {
"mandateIdentification": "2710317",
"mandateRequestIdentification": "2710317004",
"trackingIndicator": true,
"type": {
"localInstrument": {
"schema": "PROPRIETARY",
"value": "0227"
}
},
"occurrences": {
"sequenceType": "RCUR",
"frequency": {
"schema": "MonthlyFrequency",
"dayOfMonth": 15
},
"validFrom": "2019-03-05",
"firstCollectionDate": "2019-03-29"
},
"collectionAmount": {
"value": 3443.83,
"currency": "ZAR"
},
"maximumAmount": {
"value": 5165.75,
"currency": "ZAR"
},
"creditor": {
"legalName": "Creditor Name",
"identification": {
"schema": "ORGANISATION",
"identifiers": [
{
"schema": "BIC",
"BIC": "RY8PEG0L"
}
]
}
},
"creditorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "CACC"
}
},
"creditorAgent": {
"clearingSystemMemberId": {
"memberId": "430000"
}
},
"ultimateCreditor": {
"legalName": "Ultimate Creditor"
},
"debtor": {
"legalName": "Debtor Name",
"identification": {
"schema": "PERSON",
"identifiers": [
{
"identification": "I/9905140859123",
"scheme": {
"schema": "CODE",
"value": "NIDN"
}
}
]
},
"contactDetails": {
"phoneNumber": "+27-112569000",
"emailAddress": "support@debtor.com"
}
},
"debtorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "SVGS"
}
},
"debtorAgent": {
"clearingSystemMemberId": {
"memberId": "470010"
}
},
"ultimateDebtor": {
"legalName": "Ultimate Debtor"
}
}
}'Accepted. RFC9110 - 202
No contentThis operation is asynchronous. The partner responds by calling the inboundMandateAcceptanceReport operation.
Receives a mandate amendment request from Electrum when a creditor requests changes to an existing mandate. The partner should authenticate the amendment with the debtor (if required by the change type), validate the technical details, and respond with the debtor's acceptance or rejection decision.
| Scheme | Applicable |
|---|---|
| ZA_AC | ✓ |
A value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Designates which scheme a mandate operation is associated with and describes scheme-specific information for the mandate operation where relevant.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.South Africa specific supplementary data fields. These fields supplement the core mandate structure with local requirements.
Indicates the delivery and authentication mechanism of the mandate transaction.
In the ZA_AC scheme, this field dictates the specific Transaction Type (TT) processing rules that will be applied:
REAL_TIME: Maps to TT1 (non-card). The mandate request is routed over the real-time interbank switch without an upfront authentication key. Note: The actual Payer authorisation might be immediate (e.g., 120-second USSD timeout) or delayed (until the end of the day), but the routing type remains REAL_TIME.PREAUTH: Maps to TT3 (Card Present). Indicates the Payer has already been authenticated via a prior card-and-PIN transaction at the point of interaction. Mandates using this type must include the resulting Message Authentication Code (MAC) in the request payload.BATCH: Maps to TT2. The mandate request is submitted via delayed bulk file processing.NOT_APPLICABLE: Debtor authentication is not required for this action (e.g. MandateInformationRequest).The Payer's preferred recurring day for collection from their bank account.
In the ZA_AC scheme, the Collection Day is a rigid, legally binding clearing rule that is strictly evaluated relative to the mandate's Frequency. The interpretation of this integer changes based on the frequency type:
Monthly, Quarterly, Bi-annually, Annually, Once-off: Values 1 to 30 represent the exact calendar day of the month. 99 strictly represents the "Last Day" of the month (e.g., automatically adjusting for February 28th/29th). Note: 31 is not a valid input.Weekly: Values 1 to 7 represent the day of the week (1 = Monday, 7 = Sunday).Fortnightly: Values 1 to 14 represent the day within the two-week cycle (1 to 7 for week one; 8 to 14 for week two).Monthly by Rule: Values map to specific occurrences (e.g., 1 = Last Monday, 7 = First Monday, 14 = 2nd Last Day).Interbank Validation Rules: The Debtor Bank is required to store this exact day in their Mandate Register. If the mandate's dateAdjustmentRule is set to 'N' (No), the Debtor Bank will strictly validate incoming collections against this day. If a collection's Action Date does not exactly match this collectionDay (or the immediately following Processing Day), the Debtor Bank will trigger an upfront rejection.
Note: According to clearing rules, Debtor Banks are only required to enforce this strict date validation on Weekly and Monthly frequencies.
This dictates strict interbank validation rules for how collection amounts are calculated, capped, and adjusted over the life of the mandate.
The rules for each type are:
FIXED: Used for contracts where an upfront, calculated Instalment Amount is the basis for normal collections. Regular collections are strictly validated and cannot exceed this Instalment Amount. The Adjustment Category for a fixed mandate must strictly be 'NEVR' (Never).VARIABLE: Used for contracts where an upfront Instalment Amount is calculated but can be amended by the Creditor based on pre-agreed variables, such as annual increases or interest rate changes. Regular collections cannot exceed the currently active Instalment Amount.USAGE_BASED: Used for contracts where the collection amount fluctuates depending on the Payer's usage of a product or service during the payment cycle. Unlike Fixed and Variable mandates, the regular Instalment Amount is optional, and interbank validation is instead performed strictly against a mandatory Maximum Collection Amount.The Mandate Reference Number (MRN) assigned by the debtor bank upon mandate acceptance. This is the official, unique industry-wide identification number for the mandate that is unique for the mandate's entire lifecycle (including time in archives).
It is returned in the acceptance report and must be included in subsequent mandate amendment, and suspension requests.
Not to be confused with mandateIdentification (creditor's internal ID), mandateRequestTransactionIdentifier (MRTI), or mandateReference (mandate management app reference).
Structure (22 characters):
YYYYMMDD.Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
Contains the details of the mandate amendment including the reason, amended mandate, and original mandate reference.
Core mandate data structure containing all the details of a direct debit mandate.
Defines adjustment rules for mandate amounts.
Identifies the specific mechanism or channel that the Paying Bank (Debtor Bank) uses to communicate with the Payer (Debtor) to obtain their authorisation for a mandate. This field may be missing on mandate initiation/amendment and should be populated by the debtor bank upon acceptance of the mandate
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
A code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
The identification of a party, either a person or an organisation.
The name by which this party is commonly known in day to day use. For example, a shortening of their legal name or a nickname that they commonly use. This is "non-official". However, it is acceptable for this field to be set to the same as legalName.
Representation of an account for payment purposes. Note that at least one of identification or proxy is expected to be present.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
A code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
The identification of a party, either a person or an organisation.
The name by which this party is commonly known in day to day use. For example, a shortening of their legal name or a nickname that they commonly use. This is "non-official". However, it is acceptable for this field to be set to the same as legalName.
Representation of an account for payment purposes. Note that at least one of identification or proxy is expected to be present.
A code allocated to a financial or non-financial institution by the ISO 9362 Registration Authority as described in ISO 9362 Banking - Banking telecommunication messages - Business identifier code (BIC)
An organisation identified by a code allocated to a party as described in ISO 17442 Financial Services - Legal Entity Identifier (LEI).
Name by which an institution is known and which is usually used to identify that institution
Unique identification of the mandate, as assigned by the creditor. This field is used strictly by the Creditor for their own internal referencing and may be used to link collections to their related mandate. This is required for mandate initiations and cancellations.
Reference assigned to the mandate by the mandate management application. This is distinct from mandateIdentification (creditor's ID) and ZaMandatePaymentSchemeSupplementaryData.debtorBankMandateReference (debtor bank's reference).
Unique identification of the mandate request, as assigned by the creditor to the debtor when the underlying contract is concluded between the two parties. This field represents the Contract Reference Number. It appears on the debtor's bank statement to help them identify the deductions. This is required for mandate initiations and mandate cancellations.
Defines the frequency and duration of mandate collections.
Specifies the reason for a mandate action (amendment, cancellation, rejection).
Provides information to identify the underlying documents associated with the mandate
Indicates whether the mandate permits tracking for future collection instructions. Its exact meaning and relevance depend strictly on the mandate-management operation being performed:
1. Mandate Initiation & Amendment Requests
true) or revoked (false) for future collections against this mandate.2. Mandate Cancellation Requests
true: Instructs the clearing house to immediately cancel any active tracking records currently in the tracking queue for this mandate.false: Instructs the clearing house NOT to cancel records in tracking, allowing them to finish their tracking cycle despite the mandate being cancelled.3. Mandate Acceptance Reports
true or false) that was successfully saved to the Debtor Bank's Mandate Register.4. Mandate Suspensions & Information Requests
Provides details on the type of mandate.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Provides details about the reason for a mandate amendment.
Field Usage Guidelines: reason: For South African Mandate Schemes the reason for the amendment is specified as one of the below PROPRIETARY values:
MD02 - Reason has not been specified by end consumer.MD16 - Requested by Customer..MD17 - Amendment requested by Initiating Party.MD19 - Unsuspend a Mandate with changes.MD20 - Unsuspend an unchanged Mandate.MD21 - Amendment with no changes to Mandate Information.MD22 - Amendment with changes to Mandate Information.This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Specifies the reason for a mandate action (amendment, cancellation, rejection).
Identifies the value as being a pre-defined code. Always CODE.
AC01 - IncorrectAccountNumberAC04 - ClosedAccountNumberAC06 - BlockedAccountAG01 - TransactionForbiddenAG02 - InvalidBankOperationCodeAM02 - NotAllowedAmountAM03 - NotAllowedCurrencyAM05 - DuplicationBE01 - InconsistenWithEndCustomerBE04 - MissingCreditorAddressBE05 - UnrecognisedInitiatingPartyBE06 - UnknownEndCustomerBE07 - MissingDebtorAddressDT01 - InvalidDateFF01 - InvalidFileFormatMD01 - NoMandateMD02 - MissingMandatoryInformationInMandateMD07 - EndCustomerDeceasedMD08 - NoMandateServiceByAgentMD09 - NoMandateServiceOnCustomerMD10 - NoMandateServiceForSpecifiedMD11 - UnrecognisedAgentMD12 - NotUniqueMandateReferenceMD13 - IncorrectCustomerAuthenticationMD14 - IncorrectAgentMD15 - IncorrectCurrencyMD16 - RequestedByCustomerMD17 - RequestedByInitiatingPartyMD18 - RequestedByInitiatingPartyAndCustomerMD19 - MandateCancelledDueToEarlySettlementMD20 - MandateExpiredMD21 - MandateCancelledDueToFraudMD22 - MandateInitiationCancelledMD23 - MandateAmendmentCancelledMS02 - NotSpecifiedReasonCustomerGeneratedMS03 - NotSpecifiedReasonAgentGeneratedNARR - NarrativeRC01 - BankIdentifierIncorrectRF01 - NotUniqueTransactionReferenceRR01 - MissingDebtorAccountOrIdentificationRR02 - MissingDebtorNameOrAddressRR03 - MissingCreditorNameOrAddressRR04 - RegulatoryReasonSL01 - SpecificServiceOfferedByDebtorAgentSL11 - CreditorNotOnWhitelistOfDebtorSL12 - CreditorOnBlacklistOfDebtorSL13 - MaximumNumberOfDirectDebitTransactionsExceededSL14 - MaximumDirectDebitTransactionAmountExceededReference to an original mandate. The partner may identify the mandate using any of the following identifiers, depending on the context of the request and the information available. At least one of originalMandateIdentification for the original mandate, or originalMandate must be provided.
For mandate amendment, cancellation and suspension requests, originalMandate is required and the originalMandateIdentification cannot be used as the sole reference.
Core mandate data structure containing all the details of a direct debit mandate.
Identifies the original mandate-management message being referenced or responded to. For MandateInformationRequest, this block is optional on the partner request — Electrum will populate it from the latest message recorded against the mandate before forwarding to the scheme.
https://example.com/path/payments/partner-api/v1/mandates/inbound/amendment
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/inbound/amendment \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "MandateAmendmentRequest",
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"mandateRequestTransactionIdentifier": "00072019-03-05000000086",
"authenticationType": "REAL_TIME",
"requestTransmissionNumber": 1,
"collectionDay": 99,
"debitValueType": "USAGE_BASED",
"debtorBankMandateReference": "0003202501015177310122"
}
},
"messageIdentifiers": {
"messageIdentification": "100/MANOM/00210007/20190502/000040",
"creationDateTime": "2019-05-02T15:43:47Z"
},
"initiatingParty": {
"legalName": "EXAMPLE LOANS"
},
"underlyingAmendmentDetails": {
"amendmentReason": {
"reason": {
"schema": "PROPRIETARY",
"value": "MD16"
},
"additionalInformation": [
"Mandate amendment requested by creditor due to contract changes"
]
},
"amendedMandate": {
"mandateIdentification": "6858841",
"mandateRequestIdentification": "6858841001",
"trackingIndicator": true,
"type": {
"localInstrument": {
"schema": "PROPRIETARY",
"value": "0227"
}
},
"occurrences": {
"sequenceType": "RCUR",
"frequency": {
"schema": "MonthlyFrequency",
"dayOfMonth": 15
},
"validFrom": "2019-04-26",
"firstCollectionDate": "2019-04-30"
},
"collectionAmount": {
"value": 3800,
"currency": "ZAR"
},
"maximumAmount": {
"value": 5500,
"currency": "ZAR"
},
"creditor": {
"legalName": "Creditor Name",
"identification": {
"schema": "ORGANISATION",
"identifiers": [
{
"schema": "BIC",
"BIC": "RY8PEG0L"
}
]
}
},
"creditorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "CACC"
}
},
"creditorAgent": {
"clearingSystemMemberId": {
"memberId": "430000"
}
},
"debtor": {
"legalName": "Debtor Name",
"identification": {
"schema": "PERSON",
"identifiers": [
{
"identification": "I/5906140859123",
"scheme": {
"schema": "CODE",
"value": "NIDN"
}
}
]
}
},
"debtorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "SVGS"
}
},
"debtorAgent": {
"clearingSystemMemberId": {
"memberId": "990010"
}
},
"ultimateDebtor": {
"legalName": "Ultimate Debtor"
}
},
"originalMandate": {
"originalMandate": {
"mandateIdentification": "2710317",
"mandateRequestIdentification": "2710317004",
"trackingIndicator": true,
"creditor": {
"legalName": "Creditor Name",
"identification": {
"schema": "ORGANISATION",
"identifiers": [
{
"schema": "BIC",
"BIC": "RY8PEG0L"
}
]
},
"contactDetails": {
"phoneNumber": "+27-112569000",
"emailAddress": "support@creditor.com"
}
},
"debtor": {
"legalName": "Debtor Name",
"identification": {
"schema": "PERSON",
"identifiers": [
{
"identification": "I/9905140859123",
"scheme": {
"schema": "CODE",
"value": "NIDN"
}
}
]
},
"contactDetails": {
"phoneNumber": "+27-112569000",
"emailAddress": "support@debtor.com"
}
},
"debtorAgent": {
"clearingSystemMemberId": {
"memberId": "470010"
}
}
}
}
}
}'Accepted. RFC9110 - 202
No contentThis operation is asynchronous. The partner responds by calling the inboundMandateAcceptanceReport operation.
Receives a mandate cancellation request from Electrum when a creditor requests termination of an existing mandate.
If the partner maintains the mandate register, the partner should validate and process the cancellation request. Otherwise, this operation notifies the partner of a mandate cancellation validated and processed by Electrum.
| Scheme | Applicable |
|---|---|
| ZA_AC | ✓ |
A value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Designates which scheme a mandate operation is associated with and describes scheme-specific information for the mandate operation where relevant.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.South Africa specific supplementary data fields. These fields supplement the core mandate structure with local requirements.
Indicates the delivery and authentication mechanism of the mandate transaction.
In the ZA_AC scheme, this field dictates the specific Transaction Type (TT) processing rules that will be applied:
REAL_TIME: Maps to TT1 (non-card). The mandate request is routed over the real-time interbank switch without an upfront authentication key. Note: The actual Payer authorisation might be immediate (e.g., 120-second USSD timeout) or delayed (until the end of the day), but the routing type remains REAL_TIME.PREAUTH: Maps to TT3 (Card Present). Indicates the Payer has already been authenticated via a prior card-and-PIN transaction at the point of interaction. Mandates using this type must include the resulting Message Authentication Code (MAC) in the request payload.BATCH: Maps to TT2. The mandate request is submitted via delayed bulk file processing.NOT_APPLICABLE: Debtor authentication is not required for this action (e.g. MandateInformationRequest).The Payer's preferred recurring day for collection from their bank account.
In the ZA_AC scheme, the Collection Day is a rigid, legally binding clearing rule that is strictly evaluated relative to the mandate's Frequency. The interpretation of this integer changes based on the frequency type:
Monthly, Quarterly, Bi-annually, Annually, Once-off: Values 1 to 30 represent the exact calendar day of the month. 99 strictly represents the "Last Day" of the month (e.g., automatically adjusting for February 28th/29th). Note: 31 is not a valid input.Weekly: Values 1 to 7 represent the day of the week (1 = Monday, 7 = Sunday).Fortnightly: Values 1 to 14 represent the day within the two-week cycle (1 to 7 for week one; 8 to 14 for week two).Monthly by Rule: Values map to specific occurrences (e.g., 1 = Last Monday, 7 = First Monday, 14 = 2nd Last Day).Interbank Validation Rules: The Debtor Bank is required to store this exact day in their Mandate Register. If the mandate's dateAdjustmentRule is set to 'N' (No), the Debtor Bank will strictly validate incoming collections against this day. If a collection's Action Date does not exactly match this collectionDay (or the immediately following Processing Day), the Debtor Bank will trigger an upfront rejection.
Note: According to clearing rules, Debtor Banks are only required to enforce this strict date validation on Weekly and Monthly frequencies.
This dictates strict interbank validation rules for how collection amounts are calculated, capped, and adjusted over the life of the mandate.
The rules for each type are:
FIXED: Used for contracts where an upfront, calculated Instalment Amount is the basis for normal collections. Regular collections are strictly validated and cannot exceed this Instalment Amount. The Adjustment Category for a fixed mandate must strictly be 'NEVR' (Never).VARIABLE: Used for contracts where an upfront Instalment Amount is calculated but can be amended by the Creditor based on pre-agreed variables, such as annual increases or interest rate changes. Regular collections cannot exceed the currently active Instalment Amount.USAGE_BASED: Used for contracts where the collection amount fluctuates depending on the Payer's usage of a product or service during the payment cycle. Unlike Fixed and Variable mandates, the regular Instalment Amount is optional, and interbank validation is instead performed strictly against a mandatory Maximum Collection Amount.The Mandate Reference Number (MRN) assigned by the debtor bank upon mandate acceptance. This is the official, unique industry-wide identification number for the mandate that is unique for the mandate's entire lifecycle (including time in archives).
It is returned in the acceptance report and must be included in subsequent mandate amendment, and suspension requests.
Not to be confused with mandateIdentification (creditor's internal ID), mandateRequestTransactionIdentifier (MRTI), or mandateReference (mandate management app reference).
Structure (22 characters):
YYYYMMDD.Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
Contains the core details of the mandate cancellation request.
Field Usage Guidelines:
originalMessageInformation: ONLY required for in-flight cancellations (when a mandate initiation or amendment is still pending or has timed out). It identifies the specific pending message to cancel.Provides details about the reason for a mandate cancellation.
Field Usage Guidelines: reason: For South African Mandate Schemes the reason for the cancellation is specified as one of the below PROPRIETARY values:
CEXP - Contract expired.MACN - Cancellation of Mandate Amendment (Strictly used when cancelling an in-flight MandateAmendmentRequest).MICN - Cancellation of Mandate Initiation (Strictly used when cancelling an in-flight MandateInitiationRequest).MCES - Mandate Cancelled due to early settlement.MCFR - Mandate Cancellation due to Fraud.MD17 - Cancellation/amendment requested by the creditor.This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Specifies the reason for a mandate action (amendment, cancellation, rejection).
Identifies the value as being a pre-defined code. Always CODE.
AC01 - IncorrectAccountNumberAC04 - ClosedAccountNumberAC06 - BlockedAccountAG01 - TransactionForbiddenAG02 - InvalidBankOperationCodeAM02 - NotAllowedAmountAM03 - NotAllowedCurrencyAM05 - DuplicationBE01 - InconsistenWithEndCustomerBE04 - MissingCreditorAddressBE05 - UnrecognisedInitiatingPartyBE06 - UnknownEndCustomerBE07 - MissingDebtorAddressDT01 - InvalidDateFF01 - InvalidFileFormatMD01 - NoMandateMD02 - MissingMandatoryInformationInMandateMD07 - EndCustomerDeceasedMD08 - NoMandateServiceByAgentMD09 - NoMandateServiceOnCustomerMD10 - NoMandateServiceForSpecifiedMD11 - UnrecognisedAgentMD12 - NotUniqueMandateReferenceMD13 - IncorrectCustomerAuthenticationMD14 - IncorrectAgentMD15 - IncorrectCurrencyMD16 - RequestedByCustomerMD17 - RequestedByInitiatingPartyMD18 - RequestedByInitiatingPartyAndCustomerMD19 - MandateCancelledDueToEarlySettlementMD20 - MandateExpiredMD21 - MandateCancelledDueToFraudMD22 - MandateInitiationCancelledMD23 - MandateAmendmentCancelledMS02 - NotSpecifiedReasonCustomerGeneratedMS03 - NotSpecifiedReasonAgentGeneratedNARR - NarrativeRC01 - BankIdentifierIncorrectRF01 - NotUniqueTransactionReferenceRR01 - MissingDebtorAccountOrIdentificationRR02 - MissingDebtorNameOrAddressRR03 - MissingCreditorNameOrAddressRR04 - RegulatoryReasonSL01 - SpecificServiceOfferedByDebtorAgentSL11 - CreditorNotOnWhitelistOfDebtorSL12 - CreditorOnBlacklistOfDebtorSL13 - MaximumNumberOfDirectDebitTransactionsExceededSL14 - MaximumDirectDebitTransactionAmountExceededReference to an original mandate. The partner may identify the mandate using any of the following identifiers, depending on the context of the request and the information available. At least one of originalMandateIdentification for the original mandate, or originalMandate must be provided.
For mandate amendment, cancellation and suspension requests, originalMandate is required and the originalMandateIdentification cannot be used as the sole reference.
Core mandate data structure containing all the details of a direct debit mandate.
Identifies the original mandate-management message being referenced or responded to. For MandateInformationRequest, this block is optional on the partner request — Electrum will populate it from the latest message recorded against the mandate before forwarding to the scheme.
https://example.com/path/payments/partner-api/v1/mandates/inbound/cancellation
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/inbound/cancellation \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "MandateCancellationRequest",
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"mandateRequestTransactionIdentifier": "00072019-03-05000000086",
"authenticationType": "REAL_TIME",
"requestTransmissionNumber": 1,
"collectionDay": 99,
"debitValueType": "USAGE_BASED"
}
},
"messageIdentifiers": {
"messageIdentification": "100/MANCO/00999003/20240305/000001",
"creationDateTime": "2024-03-05T10:08:01Z"
},
"initiatingParty": {
"legalName": "EXAMPLE LOANS"
},
"instructingAgent": {
"clearingSystemMemberId": {
"memberId": "999003"
}
},
"instructedAgent": {
"clearingSystemMemberId": {
"memberId": "999002"
}
},
"underlyingCancellationDetails": {
"originalMessageInformation": {
"messageIdentification": "100/MANAM/00210007/20190305/000511",
"creationDateTime": "2019-03-05T10:04:44Z",
"messageNameIdentification": "MandateAmendmentRequest"
},
"cancellationReason": {
"reason": {
"schema": "PROPRIETARY",
"value": "MICN"
},
"additionalInformation": [
"Mandate cancellation requested by creditor"
]
},
"originalMandate": {
"originalMandate": {
"mandateIdentification": "33005",
"mandateRequestIdentification": "CR000000029853",
"trackingIndicator": true,
"type": {
"localInstrument": {
"schema": "PROPRIETARY",
"value": "0227"
}
},
"occurrences": {
"sequenceType": "RCUR",
"frequency": {
"schema": "MonthlyFrequency",
"dayOfMonth": 15
},
"validFrom": "2019-04-26",
"firstCollectionDate": "2019-04-30"
},
"creditor": {
"legalName": "Creditor Name",
"identification": {
"schema": "ORGANISATION",
"identifiers": [
{
"schema": "BIC",
"BIC": "RY8PEG0L"
}
]
},
"contactDetails": {
"phoneNumber": "+27-86-0001234",
"emailAddress": "collections@exampleloans.example.co.za"
}
},
"creditorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "CACC"
}
},
"creditorAgent": {
"clearingSystemMemberId": {
"memberId": "888004"
}
},
"ultimateCreditor": {
"legalName": "Ultimate Creditor Name",
"identification": {
"schema": "ORGANISATION",
"identifiers": [
{
"schema": "BIC",
"BIC": "RY8PEG0L"
}
]
},
"contactDetails": {
"phoneNumber": "+27-86-0001234",
"emailAddress": "collections@exampleloans.example.co.za"
}
},
"debtor": {
"legalName": "MR JOHN EXAMPLE"
},
"debtorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "SVGS"
}
},
"debtorAgent": {
"clearingSystemMemberId": {
"memberId": "888002"
}
}
}
}
}
}'Accepted. RFC9110 - 202
No contentThis operation is asynchronous. It is responded to by the inboundMandateStatusReport operation.
Receives a mandate suspension request from Electrum when a debtor requests suspension of an existing mandate.
If the partner maintains the mandate register, the partner should validate and process the suspension request. Otherwise, this operation notifies the partner of a mandate suspension validated and processed by Electrum.
| Scheme | Applicable |
|---|---|
| ZA_AC | ✓ |
A value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Designates which scheme a mandate operation is associated with and describes scheme-specific information for the mandate operation where relevant.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.South Africa specific supplementary data fields. These fields supplement the core mandate structure with local requirements.
Indicates the delivery and authentication mechanism of the mandate transaction.
In the ZA_AC scheme, this field dictates the specific Transaction Type (TT) processing rules that will be applied:
REAL_TIME: Maps to TT1 (non-card). The mandate request is routed over the real-time interbank switch without an upfront authentication key. Note: The actual Payer authorisation might be immediate (e.g., 120-second USSD timeout) or delayed (until the end of the day), but the routing type remains REAL_TIME.PREAUTH: Maps to TT3 (Card Present). Indicates the Payer has already been authenticated via a prior card-and-PIN transaction at the point of interaction. Mandates using this type must include the resulting Message Authentication Code (MAC) in the request payload.BATCH: Maps to TT2. The mandate request is submitted via delayed bulk file processing.NOT_APPLICABLE: Debtor authentication is not required for this action (e.g. MandateInformationRequest).The Payer's preferred recurring day for collection from their bank account.
In the ZA_AC scheme, the Collection Day is a rigid, legally binding clearing rule that is strictly evaluated relative to the mandate's Frequency. The interpretation of this integer changes based on the frequency type:
Monthly, Quarterly, Bi-annually, Annually, Once-off: Values 1 to 30 represent the exact calendar day of the month. 99 strictly represents the "Last Day" of the month (e.g., automatically adjusting for February 28th/29th). Note: 31 is not a valid input.Weekly: Values 1 to 7 represent the day of the week (1 = Monday, 7 = Sunday).Fortnightly: Values 1 to 14 represent the day within the two-week cycle (1 to 7 for week one; 8 to 14 for week two).Monthly by Rule: Values map to specific occurrences (e.g., 1 = Last Monday, 7 = First Monday, 14 = 2nd Last Day).Interbank Validation Rules: The Debtor Bank is required to store this exact day in their Mandate Register. If the mandate's dateAdjustmentRule is set to 'N' (No), the Debtor Bank will strictly validate incoming collections against this day. If a collection's Action Date does not exactly match this collectionDay (or the immediately following Processing Day), the Debtor Bank will trigger an upfront rejection.
Note: According to clearing rules, Debtor Banks are only required to enforce this strict date validation on Weekly and Monthly frequencies.
This dictates strict interbank validation rules for how collection amounts are calculated, capped, and adjusted over the life of the mandate.
The rules for each type are:
FIXED: Used for contracts where an upfront, calculated Instalment Amount is the basis for normal collections. Regular collections are strictly validated and cannot exceed this Instalment Amount. The Adjustment Category for a fixed mandate must strictly be 'NEVR' (Never).VARIABLE: Used for contracts where an upfront Instalment Amount is calculated but can be amended by the Creditor based on pre-agreed variables, such as annual increases or interest rate changes. Regular collections cannot exceed the currently active Instalment Amount.USAGE_BASED: Used for contracts where the collection amount fluctuates depending on the Payer's usage of a product or service during the payment cycle. Unlike Fixed and Variable mandates, the regular Instalment Amount is optional, and interbank validation is instead performed strictly against a mandatory Maximum Collection Amount.The Mandate Reference Number (MRN) assigned by the debtor bank upon mandate acceptance. This is the official, unique industry-wide identification number for the mandate that is unique for the mandate's entire lifecycle (including time in archives).
It is returned in the acceptance report and must be included in subsequent mandate amendment, and suspension requests.
Not to be confused with mandateIdentification (creditor's internal ID), mandateRequestTransactionIdentifier (MRTI), or mandateReference (mandate management app reference).
Structure (22 characters):
YYYYMMDD.Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
Contains the details of the mandate suspension including the reason and original mandate reference.
Reference to an original mandate. The partner may identify the mandate using any of the following identifiers, depending on the context of the request and the information available. At least one of originalMandateIdentification for the original mandate, or originalMandate must be provided.
For mandate amendment, cancellation and suspension requests, originalMandate is required and the originalMandateIdentification cannot be used as the sole reference.
Core mandate data structure containing all the details of a direct debit mandate.
Provides details about the reason for a mandate suspension.
Field Usage Guidelines: reason: For South African Mandate Schemes the reason for the suspension is specified as one of the below PROPRIETARY values:
CTAM - Contract Amended.CTCA - Contract Cancellation Initiated by Debtor.CTEX - Contract Expired.MCFC - Mandate Suspended - Final Collection.MCOC - Mandate Suspended - Once off Collection.MSUC - Mandate Suspended after seven consecutive unsuccessful Collections.MASC - Mandate Suspended - Account not in a state for Collections.MADO - Mandate suspended due to no collection for a period.This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Specifies the reason for the suspension request of a mandate.
Identifies the value as being a pre-defined code. Always CODE.
CTAM - Contract Amended.CTCA - Contract Cancellation Initiated by Debtor.CTEX - Contract Expired.MCFC - Mandate Suspended - Final Collection.MCOC - Mandate Suspended - Once off Collection.MSUC - Mandate Suspended after seven consecutive unsuccessful Collections.Suspension Request Identification A unique transaction identifier used to unambiguously identify the mandate suspension request to the clearing house.
Important: Usage of suspensionRequestIdentification**.
suspensionRequestIdentification in the MandateSuspensionRequest. The format is validated and the provided suspensionRequestIdentification is used by Electrum.suspensionRequestIdentification should not be provided by the client when initiating new mandate suspension; Electrum will generate a compliant suspensionRequestIdentification automatically which will be echoed back to the client.Lifecycle behaviour:
Structure (29 characters): The identifier is composed of 4 components separated by forward slashes (/), matching the pattern STP/<BankCode>/<Date>/<Sequence>:
STP): Fixed string indicating a Suspension.YYYY-MM-DD format.https://example.com/path/payments/partner-api/v1/mandates/inbound/suspension
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/inbound/suspension \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "MandateSuspensionRequest",
"messageIdentifiers": {
"messageIdentification": "100/SPOUT/00222290/20260319/000001",
"creationDateTime": "2026-01-26T07:58:30Z"
},
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"authenticationType": "NOT_APPLICABLE",
"requestTransmissionNumber": 1,
"debtorBankMandateReference": "001020180314DC5860BD19"
}
},
"initiatingParty": {
"legalName": "EXAMPLE LOANS"
},
"underlyingSuspensionDetails": {
"suspensionReason": {
"reason": {
"schema": "PROPRIETARY",
"value": "MCOC"
},
"additionalInformation": [
"Mandate Suspended - Once off Collection"
]
},
"originalMandate": {
"originalMandate": {
"mandateIdentification": "REGRCAP2019042615",
"mandateRequestIdentification": "REG201926123",
"trackingIndicator": true,
"type": {
"localInstrument": {
"schema": "PROPRIETARY",
"value": "0228"
}
},
"occurrences": {
"sequenceType": "RCUR",
"frequency": {
"schema": "MonthlyFrequency",
"dayOfMonth": 15
},
"validFrom": "2019-04-26",
"firstCollectionDate": "2019-04-30"
},
"collectionAmount": {
"value": 100,
"currency": "ZAR"
},
"maximumAmount": {
"value": 120,
"currency": "ZAR"
},
"creditor": {
"legalName": "Creditor Name",
"identification": {
"schema": "ORGANISATION",
"identifiers": [
{
"schema": "BIC",
"BIC": "RY8PEG0L"
}
]
}
},
"debtor": {
"legalName": "Debtor Name",
"identification": {
"schema": "PERSON",
"identifiers": [
{
"identification": "I/9905140859123",
"scheme": {
"schema": "CODE",
"value": "NIDN"
}
}
]
}
},
"debtorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "SVGS"
}
},
"debtorAgent": {
"clearingSystemMemberId": {
"memberId": "470010"
}
}
}
}
}
}'Accepted. RFC9110 - 202
No contentReceives a request from Electrum for Mandate Information to be retrieved in order to obtain the current status and details of a mandate from the authoritative Mandate Register.
This operation is asynchronous. The outcome is delivered via the inboundMandateAcceptanceReport operation.
Usage :
The debtor and creditor may be at the same bank.
| Scheme | Applicable |
|---|---|
| ZA_AC | ✓ |
A value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Designates which scheme a mandate operation is associated with and describes scheme-specific information for the mandate operation where relevant.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.South Africa specific supplementary data fields. These fields supplement the core mandate structure with local requirements.
Indicates the delivery and authentication mechanism of the mandate transaction.
In the ZA_AC scheme, this field dictates the specific Transaction Type (TT) processing rules that will be applied:
REAL_TIME: Maps to TT1 (non-card). The mandate request is routed over the real-time interbank switch without an upfront authentication key. Note: The actual Payer authorisation might be immediate (e.g., 120-second USSD timeout) or delayed (until the end of the day), but the routing type remains REAL_TIME.PREAUTH: Maps to TT3 (Card Present). Indicates the Payer has already been authenticated via a prior card-and-PIN transaction at the point of interaction. Mandates using this type must include the resulting Message Authentication Code (MAC) in the request payload.BATCH: Maps to TT2. The mandate request is submitted via delayed bulk file processing.NOT_APPLICABLE: Debtor authentication is not required for this action (e.g. MandateInformationRequest).The Payer's preferred recurring day for collection from their bank account.
In the ZA_AC scheme, the Collection Day is a rigid, legally binding clearing rule that is strictly evaluated relative to the mandate's Frequency. The interpretation of this integer changes based on the frequency type:
Monthly, Quarterly, Bi-annually, Annually, Once-off: Values 1 to 30 represent the exact calendar day of the month. 99 strictly represents the "Last Day" of the month (e.g., automatically adjusting for February 28th/29th). Note: 31 is not a valid input.Weekly: Values 1 to 7 represent the day of the week (1 = Monday, 7 = Sunday).Fortnightly: Values 1 to 14 represent the day within the two-week cycle (1 to 7 for week one; 8 to 14 for week two).Monthly by Rule: Values map to specific occurrences (e.g., 1 = Last Monday, 7 = First Monday, 14 = 2nd Last Day).Interbank Validation Rules: The Debtor Bank is required to store this exact day in their Mandate Register. If the mandate's dateAdjustmentRule is set to 'N' (No), the Debtor Bank will strictly validate incoming collections against this day. If a collection's Action Date does not exactly match this collectionDay (or the immediately following Processing Day), the Debtor Bank will trigger an upfront rejection.
Note: According to clearing rules, Debtor Banks are only required to enforce this strict date validation on Weekly and Monthly frequencies.
This dictates strict interbank validation rules for how collection amounts are calculated, capped, and adjusted over the life of the mandate.
The rules for each type are:
FIXED: Used for contracts where an upfront, calculated Instalment Amount is the basis for normal collections. Regular collections are strictly validated and cannot exceed this Instalment Amount. The Adjustment Category for a fixed mandate must strictly be 'NEVR' (Never).VARIABLE: Used for contracts where an upfront Instalment Amount is calculated but can be amended by the Creditor based on pre-agreed variables, such as annual increases or interest rate changes. Regular collections cannot exceed the currently active Instalment Amount.USAGE_BASED: Used for contracts where the collection amount fluctuates depending on the Payer's usage of a product or service during the payment cycle. Unlike Fixed and Variable mandates, the regular Instalment Amount is optional, and interbank validation is instead performed strictly against a mandatory Maximum Collection Amount.The Mandate Reference Number (MRN) assigned by the debtor bank upon mandate acceptance. This is the official, unique industry-wide identification number for the mandate that is unique for the mandate's entire lifecycle (including time in archives).
It is returned in the acceptance report and must be included in subsequent mandate amendment, and suspension requests.
Not to be confused with mandateIdentification (creditor's internal ID), mandateRequestTransactionIdentifier (MRTI), or mandateReference (mandate management app reference).
Structure (22 characters):
YYYYMMDD.Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
Contains the details of the mandate copy request including the original mandate reference.
Reference to an original mandate. The partner may identify the mandate using any of the following identifiers, depending on the context of the request and the information available. At least one of originalMandateIdentification for the original mandate, or originalMandate must be provided.
For mandate amendment, cancellation and suspension requests, originalMandate is required and the originalMandateIdentification cannot be used as the sole reference.
Core mandate data structure containing all the details of a direct debit mandate.
Identifies the original mandate-management message being referenced or responded to. For MandateInformationRequest, this block is optional on the partner request — Electrum will populate it from the latest message recorded against the mandate before forwarding to the scheme.
https://example.com/path/payments/partner-api/v1/mandates/inbound/information-request
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/inbound/information-request \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "MandateInformationRequest",
"messageIdentifiers": {
"messageIdentification": "3c004e038bd3469d99d112681ca1166f",
"creationDateTime": "2026-01-26T07:58:00Z"
},
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"authenticationType": "NOT_APPLICABLE",
"requestTransmissionNumber": 1
}
},
"initiatingParty": {
"legalName": "EXAMPLE LOANS"
},
"underlyingCopyDetails": {
"originalMandate": {
"originalMandateIdentification": "RGCAP1900000000000A1"
}
}
}'Accepted. RFC9110 - 202
No contentA value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
Provides a reference to the direct debit mandate signed between the creditor and the debtor.
Note: This model is not relevant to the ZA_EFT scheme. Electrum will not process these fields for EFT payments (e.g. tracking days are not honoured for EFT).
Specifies the original message name identifier to which the message refers. In ELPAPI, this should be the ELPAPI message type name (e.g. MandateInitiationRequest, MandateAmendmentRequest, CreditTransfer).
Designates which scheme a customer payment status report is associated with and describes scheme-specific information for the customer payment status report.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.The mandateRequestTransactionIdentifier and suspensionRequestIdentification are mutually exclusive fields
Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
Sequence number for the message's transmission. Used exclusively for real-time (TT1/TT3) messages to track message retries. 1 = original message transmission, 2-4 = retries.
Suspension Request Identification A unique transaction identifier used to unambiguously identify the mandate suspension request to the clearing house.
Important: Usage of suspensionRequestIdentification**.
suspensionRequestIdentification in the MandateSuspensionRequest. The format is validated and the provided suspensionRequestIdentification is used by Electrum.suspensionRequestIdentification should not be provided by the client when initiating new mandate suspension; Electrum will generate a compliant suspensionRequestIdentification automatically which will be echoed back to the client.Lifecycle behaviour:
Structure (29 characters): The identifier is composed of 4 components separated by forward slashes (/), matching the pattern STP/<BankCode>/<Date>/<Sequence>:
STP): Fixed string indicating a Suspension.YYYY-MM-DD format.APPROVED: The instruction has been approved.CANCELLED: The instruction has been cancelled.PENDING: The instruction is pending.REJECTED: The instruction has been rejected.https://example.com/path/payments/partner-api/v1/mandates/inbound/status-report
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/inbound/status-report \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "CustomerPaymentStatusReport",
"messageIdentifiers": {
"messageIdentification": "100/MANSR/00210010/20190513/000001",
"creationDateTime": "2019-05-13T15:16:00Z"
},
"originalMessageIdentifiers": {
"messageIdentification": "100/MANIN/00210007/20190305/000511",
"creationDateTime": "2019-03-05T10:04:44Z"
},
"originalMessageNameIdentification": "MandateInitiationRequest",
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"mandateRequestTransactionIdentifier": "00072019-03-05000000086",
"requestTransmissionNumber": 1
}
},
"status": {
"outcome": "PENDING",
"reasonInfo": [
{
"reason": {
"schema": "CODE",
"value": "ACTC"
},
"additionalInformation": "Mandate initiation request validated. Awaiting debtor authentication."
}
]
},
"mandateInformation": {
"mandateIdentification": "REGRCAP2019042615"
}
}'Accepted. RFC9110 - 202
No contentThis operation is asynchronous.
Use cases include:
Invoked to indicate whether the mandate suspension was accepted or rejected.
| Scheme | Applicable |
|---|---|
| ZA_AC | ✓ |
A value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
Provides a reference to the direct debit mandate signed between the creditor and the debtor.
Note: This model is not relevant to the ZA_EFT scheme. Electrum will not process these fields for EFT payments (e.g. tracking days are not honoured for EFT).
Specifies the original message name identifier to which the message refers. In ELPAPI, this should be the ELPAPI message type name (e.g. MandateInitiationRequest, MandateAmendmentRequest, CreditTransfer).
Designates which scheme a customer payment status report is associated with and describes scheme-specific information for the customer payment status report.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.The mandateRequestTransactionIdentifier and suspensionRequestIdentification are mutually exclusive fields
Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
Sequence number for the message's transmission. Used exclusively for real-time (TT1/TT3) messages to track message retries. 1 = original message transmission, 2-4 = retries.
Suspension Request Identification A unique transaction identifier used to unambiguously identify the mandate suspension request to the clearing house.
Important: Usage of suspensionRequestIdentification**.
suspensionRequestIdentification in the MandateSuspensionRequest. The format is validated and the provided suspensionRequestIdentification is used by Electrum.suspensionRequestIdentification should not be provided by the client when initiating new mandate suspension; Electrum will generate a compliant suspensionRequestIdentification automatically which will be echoed back to the client.Lifecycle behaviour:
Structure (29 characters): The identifier is composed of 4 components separated by forward slashes (/), matching the pattern STP/<BankCode>/<Date>/<Sequence>:
STP): Fixed string indicating a Suspension.YYYY-MM-DD format.APPROVED: The instruction has been approved.CANCELLED: The instruction has been cancelled.PENDING: The instruction is pending.REJECTED: The instruction has been rejected.https://example.com/path/payments/partner-api/v1/mandates/outbound/status-report
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/outbound/status-report \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "CustomerPaymentStatusReport",
"messageIdentifiers": {
"messageIdentification": "100/MANSR/00210010/20190513/000001",
"creationDateTime": "2019-05-13T15:16:00Z"
},
"originalMessageIdentifiers": {
"messageIdentification": "100/MANIN/00210007/20190305/000511",
"creationDateTime": "2019-03-05T10:04:44Z"
},
"originalMessageNameIdentification": "MandateInitiationRequest",
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"mandateRequestTransactionIdentifier": "00072019-03-05000000086",
"requestTransmissionNumber": 1
}
},
"status": {
"outcome": "PENDING",
"reasonInfo": [
{
"reason": {
"schema": "CODE",
"value": "ACTC"
},
"additionalInformation": "Mandate initiation request validated. Awaiting debtor authentication."
}
]
},
"mandateInformation": {
"mandateIdentification": "REGRCAP2019042615"
}
}'Accepted. RFC9110 - 202
No contentA value used to trace an HTTP message within an Electrum Regulated Payments implementation. This field must be set as per the traceparent element defined in the W3C Trace Context Level 2 specification.
A value used to provide context to an HTTP message as it is traced within an Electrum Regulated Payments implementation. This field must be set as per the tracestate element defined in the W3C Trace Context Level 2 specification.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.
Holds a point-to-point unique message identification string as well as a message's creation date time.
The date and time at which the message was created, in senders local timezone or UTC. The date must be formatted as defined by date-time in RFC3339
This model is the basic representation of a Party. It is expanded on depending on whether the party is a person or an organisation.
Designates which scheme a mandate operation is associated with and describes scheme-specific information for the mandate operation where relevant.
Identifies the scheme used for the payment
ZA_RTC: South African Realtime Clearing scheme.ZA_RPP: South African Realtime Payments Platform scheme.ZA_EFT: South African Electronic Funds Transfer scheme.ZA_AC : South African Authenticated Collections scheme.ZA_RMS: South African Registered Mandate Service scheme.CBPR_PLUS: Cross-Border Payments and Reporting Plus.South Africa specific supplementary data fields. These fields supplement the core mandate structure with local requirements.
Indicates the delivery and authentication mechanism of the mandate transaction.
In the ZA_AC scheme, this field dictates the specific Transaction Type (TT) processing rules that will be applied:
REAL_TIME: Maps to TT1 (non-card). The mandate request is routed over the real-time interbank switch without an upfront authentication key. Note: The actual Payer authorisation might be immediate (e.g., 120-second USSD timeout) or delayed (until the end of the day), but the routing type remains REAL_TIME.PREAUTH: Maps to TT3 (Card Present). Indicates the Payer has already been authenticated via a prior card-and-PIN transaction at the point of interaction. Mandates using this type must include the resulting Message Authentication Code (MAC) in the request payload.BATCH: Maps to TT2. The mandate request is submitted via delayed bulk file processing.NOT_APPLICABLE: Debtor authentication is not required for this action (e.g. MandateInformationRequest).The Payer's preferred recurring day for collection from their bank account.
In the ZA_AC scheme, the Collection Day is a rigid, legally binding clearing rule that is strictly evaluated relative to the mandate's Frequency. The interpretation of this integer changes based on the frequency type:
Monthly, Quarterly, Bi-annually, Annually, Once-off: Values 1 to 30 represent the exact calendar day of the month. 99 strictly represents the "Last Day" of the month (e.g., automatically adjusting for February 28th/29th). Note: 31 is not a valid input.Weekly: Values 1 to 7 represent the day of the week (1 = Monday, 7 = Sunday).Fortnightly: Values 1 to 14 represent the day within the two-week cycle (1 to 7 for week one; 8 to 14 for week two).Monthly by Rule: Values map to specific occurrences (e.g., 1 = Last Monday, 7 = First Monday, 14 = 2nd Last Day).Interbank Validation Rules: The Debtor Bank is required to store this exact day in their Mandate Register. If the mandate's dateAdjustmentRule is set to 'N' (No), the Debtor Bank will strictly validate incoming collections against this day. If a collection's Action Date does not exactly match this collectionDay (or the immediately following Processing Day), the Debtor Bank will trigger an upfront rejection.
Note: According to clearing rules, Debtor Banks are only required to enforce this strict date validation on Weekly and Monthly frequencies.
This dictates strict interbank validation rules for how collection amounts are calculated, capped, and adjusted over the life of the mandate.
The rules for each type are:
FIXED: Used for contracts where an upfront, calculated Instalment Amount is the basis for normal collections. Regular collections are strictly validated and cannot exceed this Instalment Amount. The Adjustment Category for a fixed mandate must strictly be 'NEVR' (Never).VARIABLE: Used for contracts where an upfront Instalment Amount is calculated but can be amended by the Creditor based on pre-agreed variables, such as annual increases or interest rate changes. Regular collections cannot exceed the currently active Instalment Amount.USAGE_BASED: Used for contracts where the collection amount fluctuates depending on the Payer's usage of a product or service during the payment cycle. Unlike Fixed and Variable mandates, the regular Instalment Amount is optional, and interbank validation is instead performed strictly against a mandatory Maximum Collection Amount.The Mandate Reference Number (MRN) assigned by the debtor bank upon mandate acceptance. This is the official, unique industry-wide identification number for the mandate that is unique for the mandate's entire lifecycle (including time in archives).
It is returned in the acceptance report and must be included in subsequent mandate amendment, and suspension requests.
Not to be confused with mandateIdentification (creditor's internal ID), mandateRequestTransactionIdentifier (MRTI), or mandateReference (mandate management app reference).
Structure (22 characters):
YYYYMMDD.Mandate Request Transaction Identifier (MRTI) A unique transaction identifier used for matching multiple messages to a single transaction. This identifier is created for each new mandate request to uniquely identify the transaction within the Authenticated Collections scheme.
Important: Usage of mandateRequestTransactionIdentifier**.
MRTI. The format is validated and the provided MRTI is used by Electrum.MRTI should not be provided by the client when initiating new mandate transactions; Electrum will generate a compliant MRTI automatically which will be echoed back to the client.Structure (23 characters):
YYYY-MM-DD. Must be a valid date.Lifecycle behaviour:
MRTI for the initiation request. If not provided by the client, Electrum generates one automatically.MRTI is required for the amendment request. If not provided by the client, Electrum generates one automatically. The amendment is linked back to the original mandate using the Mandate Reference Number (MRN).MRTI must exactly match the MRTI of the in-flight request being cancelled. If not provided, Electrum handles this automatically by retrieving the MRTI of the in-flight transaction.MRTI must be issued for the cancellation request. If not provided, Electrum determines the mandate state and applies the correct rule automatically.MRTI from the request being responded to. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.MRTI from the request being reported on. For API-level correlation, clients use originalMessageIdentifiers.messageIdentification instead.Validation rules enforced by the scheme:
Contains the core information regarding the acceptance or rejection of the mandate maintenance request.
Result of a mandate maintenance request.
Indicates whether the mandate maintenance request was accepted (true) or rejected (false).
Additional information about the rejection reason.
Reference to an original mandate. The partner may identify the mandate using any of the following identifiers, depending on the context of the request and the information available. At least one of originalMandateIdentification for the original mandate, or originalMandate must be provided.
For mandate amendment, cancellation and suspension requests, originalMandate is required and the originalMandateIdentification cannot be used as the sole reference.
Identifies the original mandate-management message being referenced or responded to. For MandateInformationRequest, this block is optional on the partner request — Electrum will populate it from the latest message recorded against the mandate before forwarding to the scheme.
https://example.com/path/payments/partner-api/v1/mandates/outbound/acceptance-report
curl -i -X POST \
https://example.com/path/payments/partner-api/v1/mandates/outbound/acceptance-report \
-H 'Content-Type: application/json' \
-H 'traceparent: string' \
-H 'tracestate: string' \
-d '{
"schema": "MandateAcceptanceReport",
"messageIdentifiers": {
"messageIdentification": "3c004e038bd3469d99d112681ca1166f",
"creationDateTime": "2019-05-13T15:15:43Z"
},
"originalMessageIdentifiers": {
"messageIdentification": "100/MANIN/00210007/20190305/000511",
"creationDateTime": "2019-03-05T10:04:44Z"
},
"paymentScheme": {
"schema": "ZA_AC",
"schemeData": {
"mandateRequestTransactionIdentifier": "00072018-03-19000000098",
"debtorBankMandateReference": "0003202501015177310122",
"authenticationType": "REAL_TIME",
"requestTransmissionNumber": 1,
"collectionDay": 30,
"debitValueType": "FIXED"
}
},
"initiatingParty": {
"legalName": "EXAMPLE LOANS"
},
"underlyingAcceptanceDetails": {
"acceptanceResult": {
"accepted": false,
"rejectionReason": {
"schema": "PROPRIETARY",
"value": "NRSP"
},
"additionalRejectionInformation": [
"Mandate initiation timed out waiting for debtor authorisation"
]
},
"originalMandate": {
"originalMandate": {
"mandateIdentification": "REGRCAP2019042615",
"mandateRequestIdentification": "REG201926123",
"trackingIndicator": true,
"type": {
"localInstrument": {
"schema": "PROPRIETARY",
"value": "0228"
}
},
"occurrences": {
"sequenceType": "RCUR",
"frequency": {
"schema": "MonthlyFrequency",
"dayOfMonth": 15
},
"validFrom": "2019-04-26",
"firstCollectionDate": "2019-04-30"
},
"collectionAmount": {
"value": 100,
"currency": "ZAR"
},
"maximumAmount": {
"value": 120,
"currency": "ZAR"
},
"creditor": {
"legalName": "Creditor Name",
"identification": {
"schema": "ORGANISATION",
"identifiers": [
{
"schema": "BIC",
"BIC": "RY8PEG0L"
}
]
}
},
"debtor": {
"legalName": "Debtor Name",
"identification": {
"schema": "PERSON",
"identifiers": [
{
"identification": "I/9905140859123",
"scheme": {
"schema": "CODE",
"value": "NIDN"
}
}
]
}
},
"debtorAccount": {
"identification": {
"schema": "GENERIC",
"scheme": {
"schema": "PROPRIETARY",
"value": "ACCOUNT_NUMBER"
},
"value": "10173412345"
},
"type": {
"schema": "CODE",
"value": "SVGS"
}
},
"debtorAgent": {
"clearingSystemMemberId": {
"memberId": "470010"
}
},
"authentication": {
"date": "2019-04-03",
"channel": {
"schema": "PROPRIETARY",
"value": "NC03"
}
}
}
}
}
}'Accepted. RFC9110 - 202
No content