Client-supplied correlation ID echoed in response headers for tracing.
Idempotency key for safe retry of POST requests. Duplicate submissions with the same key return the cached response.
<= 64 characters
Complete ISO 20022 message in — all party addresses discovered and processed
automatically via XPath registry.
Message-level equivalent of EP-01. Submit a complete ISO 20022 message — ARS
discovers all party addresses via XPath registry, applies the correct
PostalAddress24 variant per role, and runs the full 7-step pipeline.
XPath registry covers:
Either messageContent or messageXml required. If both, messageXml takes precedence.
OCT_INST: payer address always mandatory regardless of EEA status.
Processing precedence: channelProfile → processingOptions → context.
Client-supplied correlation ID echoed in response headers for tracing.
Idempotency key for safe retry of POST requests. Duplicate submissions with the same key return the cached response.
<= 64 characters
EP-08 request. Full ARS AutoCorrect on all party addresses in an ISO 20022 message.
Name of a registered channelProfile. Loads scheme, direction, outputMode, and other defaults.
Transaction execution datetime for SR2026 cutover enforcement.
JSON equivalent of the ISO 20022 message. One of messageContent or messageXml required.
Raw ISO 20022 XML string. Takes precedence over messageContent if both provided.
Per-request overrides of the channelProfile configuration. Only fields present
here override the corresponding channelProfile value. Fields absent here fall
through to channelProfile. This is NOT a general-purpose configuration block —
it only overrides values already set in channelProfile.
Analytics/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.
Message processing completed
Top-level processing decision.
Allowed values:ACCEPTREJECTPARTIAL_SUCCESS
ISO 20022 message type. R-transaction types (pain.002, pain.007, pacs.002,
pacs.004, camt.029, camt.052, camt.053, camt.054, camt.055, camt.056, camt.058, camt.110, camt.111) must be submitted to R-transaction endpoints only
(EP-07, EP-15). Submitting them to Check/Convert endpoints returns HTTP 422 (REG-06).
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
Payment scheme identifier.
Allowed values:SCTSCT_INSTSDD_CORESDD_B2BOCT_INSTCBPRPLUSCHAPST2EURO1FEDWIREOTHER
Full address processing result object (used in EP-01 and all Layer 1 responses).
Processing statistics block returned on all endpoints.
Legacy issue object. Preserved for backward compatibility with v4.0 integrations.
New integrations should use reasons[] instead.
Batch version of EP-08. Accepts up to 100 complete ISO messages per call.
Each message processed independently through the full pipeline.
Requires HTTP Message Signature (RFC 9421) and Idempotency-Key header in production.
Maximum 100 messages per call.
Processing precedence: channelProfile → processingOptions → context.
Client-supplied correlation ID echoed in response headers for tracing.
Idempotency key for safe retry of POST requests. Duplicate submissions with the same key return the cached response.
<= 64 characters
SHA-256 digest of the request body (RFC 9530). Required input for HTTP
Message Signature verification on this request. Optional in sandbox;
required in production for operations that mandate signing (see operation
description).
HTTP Message Signature (RFC 9421) over the request, including the
Content-Digest header. Optional in sandbox; required in production for
operations that mandate signing (see operation description).
Signature metadata (RFC 9421) — identifies the signature algorithm,
covered components, and key identifier used to produce the Signature
header. Required whenever Signature is present.
EP-09 batch request. Up to 100 messages per call.
<= 100 items
Analytics/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.
Batch message processing completed
Top-level processing decision.
Allowed values:ACCEPTREJECTPARTIAL_SUCCESS
Processing statistics block returned on all endpoints.
Message-level structural validation. Discovers all party addresses, classifies each,
and runs structural validation. No postal DB, no conversion.
Typical workflow: Check → COMPLIANT: transmit. NOT_COMPLIANT: call EP-12 (AutoCorrect).
v4.2 change: No longer performs postal DB verification.
R-transaction types return HTTP 422 REG-06.
Processing precedence: channelProfile → processingOptions → context.
Client-supplied correlation ID echoed in response headers for tracing.
EP-10 request. Structural PreCheck on all party addresses in message.
Per-request overrides of the channelProfile configuration. Only fields present
here override the corresponding channelProfile value. Fields absent here fall
through to channelProfile. This is NOT a general-purpose configuration block —
it only overrides values already set in channelProfile.
Analytics/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.
Message check completed
Outcome of structural pre-check validation.
Allowed values:COMPLIANTNOT_COMPLIANT
Message-level equivalent of EP-06. Discovers and classifies every party address in a
submitted ISO 20022 message. No validation, verification, or conversion.
No issues[] or reasons[] in response. Context fields are analytics only.
Very low latency — ideal for routing decisions and dashboard aggregation.
Processing precedence: channelProfile → processingOptions → context.
Client-supplied correlation ID echoed in response headers for tracing.
EP-11 request. Classification of all party addresses in message.
Analytics only for this endpoint.
Message classification completed
ISO 20022 message type. R-transaction types (pain.002, pain.007, pacs.002,
pacs.004, camt.029, camt.052, camt.053, camt.054, camt.055, camt.056, camt.058, camt.110, camt.111) must be submitted to R-transaction endpoints only
(EP-07, EP-15). Submitting them to Check/Convert endpoints returns HTTP 422 (REG-06).
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
Payment scheme identifier.
Allowed values:SCTSCT_INSTSDD_CORESDD_B2BOCT_INSTCBPRPLUSCHAPST2EURO1FEDWIREOTHER