Skip to main content
POST
SI Status

When to Use

Check the current lifecycle state of a standing-instruction mandate — e.g., whether it’s still active, how many debits have been processed, and how many remain. Applies to on-demand and auto debit mandates (PayDirect and PayCollect). See Standing Instruction Sale in the API Reference sidebar.

Mandate Status Values

Example Data Payloads

Active mandate:
Exhausted mandate:

Authorizations

x-gl-token-external
string
header
required

RSA-signed JWS (JSON Web Signature) token carrying the request payload.

  • Header: { "alg": "RS256", "kid": "<merchant-key-id>", "iss": "<merchant-id>", "x-gl-enc": "false", "is-digested": "true" }
  • Payload: the exact JSON body sent in the request (or its SHA-256 digest when is-digested=true).
  • Signed with the merchant's RSA private key; PayGlocal verifies with the matching public key. Used by all /gl/v1/payments/* endpoints.

Body

application/json
mandateId
string
required

PayGlocal-issued mandate identifier.

Example:

"mandate_abc123"

Response

Mandate status retrieved.

Standard PayGlocal response envelope (GlocalApiResponse).

gid
string

PayGlocal global transaction ID.

Example:

"gl_9c2645ed09edb22e"

status
string

High-level status of this API response.

Example:

"SUCCESS"

message
string

Human-readable message.

timestamp
string

Response timestamp (DD/MM/YYYY HH:MM:SS).

Example:

"10/01/2026 15:00:00"

reasonCode
string

Empty on success; populated on failure.

Example:

""

data
object

Operation-specific payload. Shape varies by endpoint.

errors
object

Field-level validation errors (populated on 4xx).