Context
objectAnalytics/audit passthrough AND processing fallback layer.
Fields labelled “Analytics + Processing fallback” are used as last-resort defaults
when both channelProfile and processingOptions leave a parameter unresolved.
Pure analytics fields are written to the ARS audit log but do not affect processing.
Processing precedence: channelProfile → processingOptions → context.
Analytics only. ISO 20022 party name used for entity conflict detection.
Analytics + Processing fallback. Payment scheme.
Allowed values:SCTSCT_INSTSDD_CORESDD_B2BOCT_INSTCBPRPLUSCHAPST2EURO1FEDWIREOTHER
Analytics + Processing fallback. SR2025 or SR2026. Controls post-cutover enforcement.
Allowed values:SR2025SR2026
Analytics + Processing fallback. Payment execution datetime in ISO 8601 UTC. Used for SR2026 cutover enforcement (cutover = 2026-11-15T02:30:00Z).
Analytics + Processing fallback. OUTBOUND | INBOUND.
Allowed values:OUTBOUNDINBOUND
Analytics + Processing fallback. Party role for this request.
Allowed values:debtorcreditorultimate_debtorultimate_creditorinitiating_party
Analytics + Processing fallback. Address line rendering constraints.
Allowed values:EPCCBPR_PLUSMT_LEGACYCOMPLIANCE
Analytics + Processing fallback. Country of the sending PSP (ISO 3166-1 alpha-2).
Match pattern:^[A-Z]{2}$
Analytics + Processing fallback. Country of the receiving PSP.
Match pattern:^[A-Z]{2}$
Analytics + Processing fallback. ISO 20022 message type.
Allowed values:pain.001pain.002pain.007pain.008pacs.002pacs.003pacs.004pacs.008pacs.009pacs.010camt.029camt.052camt.053camt.054camt.055camt.056camt.057camt.058camt.060camt.105camt.106camt.107camt.108camt.109camt.110camt.111
Analytics + Processing fallback. IANA timezone for executionDatetime evaluation.
Analytics only. Format of the originating input.
Allowed values:FULLY_STRUCTUREDHYBRIDFULLY_UNSTRUCTURED
Analytics only. Expected output format.
Allowed values:FULLY_STRUCTUREDHYBRIDFULLY_UNSTRUCTURED
Analytics only. Sending system identifier (e.g. PAYMENT_HUB, SWIFT_ALLIANCE).
Analytics only. BIC of the sending institution.
Analytics only. BIC of the receiving institution.
Analytics only. Payment method for audit reporting.
Analytics only. Delivery channel for audit.
Allowed values:apifileother
Analytics only. Caller application identifier.
Analytics only. Business reference for audit trail (e.g. payment ID, batch ID).
Analytics only. Whether the party is a company or individual.
Allowed values:COMPANYINDIVIDUAL
ReasonCode
objectStructured reason code. Prefix indicates category (each family drawn from
the internal rules registry — clients should not depend on the exact
numeric value):
Customer-facing regulatory / processing families:
FMT = format-validation, FLD = field-required, REG = regulatory,
CNV = conversion, ENT = entity, VRF = verification.
Diagnostic / algorithmic families (INFO-severity only):
RFT = reformatting, INF = informational, DCT = dictionary match,
POS = positional-rule, SYN = syntax-rule, VLD = validation,
ENR = enrichment, ADP = adaptive-parser, DIC = dictionary lookup,
GLC = geo-location, PHN = phonetic, SPL = spell-correction,
VAL = validation-diagnostic.
All codes use the strict PREFIX-NNN (3-digit) format.
Reason code in the strict PREFIX-NNN (3-letter prefix, hyphen,
3-digit number) format. Examples: FMT-001 (format-validation
ERROR), REG-005 (regulatory), CNV-008 (conversion),
INF-107 (informational diagnostic). Clients should treat the
whole code as an opaque identifier and match on the full string.
Match pattern:^[A-Z]{3}-\d{3}$
Example:REG-005
Severity level.
Allowed values:ERRORWARNINGINFO
ISO 20022 field name the reason applies to (e.g. TownName, AddressLine).
Human-readable explanation.
Regulatory reference (e.g. EPC SCT Rulebook §3.4, CBPR+ MP §2.1).
0-based index of the addressLine[] entry the reason came from. Populated only when field == “addressLine”.
Where the rule applies. Useful for filtering by processing phase.
Allowed values:PreCheckAutoCorrectBoth
Fields that fed into this reason. Aids caller in identifying which inputs to fix.
Example:streetName, buildingNumber
Issue
objectLegacy issue object. Preserved for backward compatibility with v4.0 integrations.
New integrations should use reasons[] instead.
Allowed values:ERRORWARNINGINFO
ISO 20022 XML tag the issue anchors to (e.g. TwnNm, PstCd, AdrLine).
Example:TwnNm
Regulation or rulebook reference (e.g. EPC153-22 §7, PMPG v1.11 §5).
Example:EPC153-22 §7
Statistics
objectProcessing statistics block returned on all endpoints.
Total processing time in milliseconds.
Total number of records submitted.
Number of records successfully processed.
Records that produced one or more WARNING reasons but were not rejected.
Records that failed with an unrecoverable ERROR (distinct from rejectedCount which counts business-rule rejects).
RTransactionContext
objectR-transaction exemption assessment result.
TRUE if original predates SR2026 cutover and exemption applies; FALSE if postdates; null if originalExecutionDatetime not provided.
Always 2026-11-15T02:30:00Z — the SR2026 cutover reference datetime.
Example:2026-11-15T02:30:00Z
TRUE if the original payment execution datetime predates the SR2026 cutover.