Request identifier information synchronously

This operation is synchronous.

The inbound identifier determination operation can be called to resolve additional information about an identifier, for example to resolve a proxy.

In the context of an inbound payment, Electrum sends an identifier determination to the partner for processing.

Scheme Applicable Function Enabled
ZA_EFT N/A
ZA_RPP Proxy Resolution - Validate a proxy and return additional information for use in a subsequent credit transfer
ZA_RTC N/A
Request
header Parameters
traceparent
string (traceparent) ^[A-Fa-f0-9]{2}\-[A-Fa-f0-9]{32}\-[A-Fa-f0-9]...

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 (V2))[https://www.w3.org/TR/trace-context-2/].

tracestate
string (tracestate) ^[A-Za-z0-9=, _\*/@]{0,1024}$

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 traceparent element defined in the (W3C Trace Context Level 2 specification (V2))[https://www.w3.org/TR/trace-context-2/].

Request Body schema: application/json
required
object (MessageIdentifiers)

Holds a point-to-point unique message identification string as well as a message's creation date time.

object (SupplementaryData)

A list of key-value pairs to support adding any supplementary/additional data to an Electrum Regulated Payments API message.

required
object (DeterminationRequest)
schema
required
string
Value: "IdentifierDeterminationRequest"
Responses
200

OK. RFC9110 - 200

Note that a response containing a 200 (OK) HTTP status does not necessarily mean that the response contains a positive outcome but rather that the Partner successfully processed the request and is providing a response. The functional outcome might still be a negative one (e.g. the identifier was not found). In the event that the partner encounters a technical error when processing a synchronous identifier determination request, the appropriate 4xx or 5xx response should be used.

400

Bad request. RFC9110 - 400

401

Unauthorized. RFC9110 - 401

403

Forbidden. RFC9110 - 403

405

Method not allowed. RFC9110 - 405

409

Conflict. RFC9110 - 409

422

Unprocessable content. RFC9110 - 422

500

Internal server error. RFC9110 - 500

503

Service unavailable. RFC9110 - 503

post/identifiers/inbound/identifier-determination-sync
Request samples
application/json
{
  • "messageIdentifiers": {
    },
  • "schema": "IdentifierDeterminationRequest",
  • "request": {
    },
  • "supplementaryData": {
    }
}
Response samples
application/json
{
  • "schema": "IdentifierDeterminationResponse",
  • "messageIdentifiers": {
    },
  • "originalMessageIdentifiers": {
    },
  • "report": {
    },
  • "supplementaryData": {
    }
}
Copyright © Electrum Payments (Pty) Ltd. 2019-2023. All right reserved.