GPI Tracking Status Lookup
Interpret actual chronological GPI status ledger through caller verified edition mappings, flag conflicting terminal evidence; mapped credit not independent beneficiary receipt proof. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.
Description
Payment tracking uses status histories and a particular status-code mapping.
Payment tracking uses status histories and a particular status-code mapping.1
A terminal status differs from a credited status and neither is inferred from a generic label alone. Use GPI Tracking Status Lookup to evaluate the supplied inputs under the model explained below.
When to use GPI Tracking Status Lookup
Use GPI Tracking Status Lookup to evaluate the supplied inputs under the model explained below. Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
How to use GPI Tracking Status Lookup and understand its results
- Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
- Enter Caller gpi status ids, Caller terminal flags, Caller credited flags, Observed status ids, Observed status times civil days using the field table and validation rules below, then run the tool.
- Read Latest observed status id, Caller mapped terminal, Caller mapped credited, Prior terminal status conflict; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerGpiStatusIds | Caller gpi status ids | array of string | Required; constraints below |
| callerTerminalFlags | Caller terminal flags | array of number | Required; constraints below |
| callerCreditedFlags | Caller credited flags | array of number | Required; constraints below |
| observedStatusIds | Observed status ids | array of string | Required; constraints below |
| observedStatusTimesCivilDays | Observed status times civil days | array of number | Required; constraints below |
Enter unique nonblank caller status IDs with aligned binary terminal and credited flags, then nonempty observed statuses and aligned nonnegative nondecreasing finite time coordinates. Equal timestamps are allowed; order is supplied rather than sorted. Each observed status must exist in the catalog. Return the final status and its mapped flags. Conflict means an earlier terminal status has a different catalog index from the final status; repeated identical terminal status does not conflict. No live SWIFT query or credited-payment verification occurs.
latest=last supplied status; conflict=earlierTerminal AND earlierStatus!=latestStatus Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| latestObservedStatusId | Latest observed status id | string |
| callerMappedTerminal | Caller mapped terminal | boolean |
| callerMappedCredited | Caller mapped credited | boolean |
| priorTerminalStatusConflict | Prior terminal status conflict | boolean |
{
"input": {
"callerGpiStatusIds": [
"ACSP",
"ACCC"
],
"callerTerminalFlags": [
0,
1
],
"callerCreditedFlags": [
0,
1
],
"observedStatusIds": [
"ACSP",
"ACCC"
],
"observedStatusTimesCivilDays": [
1,
2
]
},
"output": {
"latestObservedStatusId": "ACCC",
"callerMappedTerminal": true,
"callerMappedCredited": true,
"priorTerminalStatusConflict": false
}
}Limitations and assumptions
A terminal status differs from a credited status and neither is inferred from a generic label alone. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Notional Pooling Multicurrency Offset No Settlement Lookup for a related task: Notional pooling can offset balances for interest calculations without moving each balance.
Use MT799 Free Format Pre Advice Versus Binding Note Lookup for a related task: A free-format bank message conveys text within a messaging standard.
References
-
GPI Tracking Status Lookup — tool.io
Similar or alternative tools
- Notional Pooling Multicurrency Offset No Settlement Lookup
Notional pooling can offset balances for interest calculations without moving each balance.
- MT799 Free Format Pre Advice Versus Binding Note Lookup
A free-format bank message conveys text within a messaging standard.