RTP FedNow Instant Availability Lookup
Screen RTP/FedNow availability against independently verified endpoints, amount limits and current operational evidence;24/7 label alone never establishes availability. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.
Description
Instant-payment availability depends on amount limits, participant enablement and operational evidence.
Instant-payment availability depends on amount limits, participant enablement and operational evidence.1
A scenario check does not query live rail status or execute a payment. Use RTP FedNow Instant Availability Lookup to evaluate the supplied inputs under the model explained below.
When to use RTP FedNow Instant Availability Lookup
Use RTP FedNow Instant Availability 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 RTP FedNow Instant Availability Lookup and understand its results
- Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
- Enter Caller instant rail ids, Caller rail amount limits minor, Caller sender enabled flags, Caller receiver enabled flags, Caller service operational known flags, Caller service operational flags, Transaction minor using the field table and validation rules below, then run the tool.
- Read Available instant rail ids, Unknown operational rail ids; 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 |
|---|---|---|---|
| callerInstantRailIds | Caller instant rail ids | array of string | Required; constraints below |
| callerRailAmountLimitsMinor | Caller rail amount limits minor | array of number | Required; constraints below |
| callerSenderEnabledFlags | Caller sender enabled flags | array of number | Required; constraints below |
| callerReceiverEnabledFlags | Caller receiver enabled flags | array of number | Required; constraints below |
| callerServiceOperationalKnownFlags | Caller service operational known flags | array of number | Required; constraints below |
| callerServiceOperationalFlags | Caller service operational flags | array of number | Required; constraints below |
| transactionMinor | Transaction minor | number | Required; constraints below |
Enter unique nonblank rail IDs with aligned nonnegative integer limits no greater than 1000000000000 and binary sender, receiver, operational-known and operational flags, plus a transaction in that monetary range. Candidate eligibility requires amount≤limit and both endpoints enabled. Return candidates whose service is known operational separately from candidates with unknown operations. Known nonoperational rails are excluded; unknown placeholders do not become availability. No live status check or transfer is performed.
eligible=amount≤limit and senderEnabled and receiverEnabled; available=eligible and known and operational Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| availableInstantRailIds | Available instant rail ids | array |
| unknownOperationalRailIds | Unknown operational rail ids | array of string |
{
"input": {
"callerInstantRailIds": [
"rtp",
"fednow"
],
"callerRailAmountLimitsMinor": [
1000,
2000
],
"callerSenderEnabledFlags": [
1,
1
],
"callerReceiverEnabledFlags": [
0,
1
],
"callerServiceOperationalKnownFlags": [
1,
0
],
"callerServiceOperationalFlags": [
1,
1
],
"transactionMinor": 500
},
"output": {
"availableInstantRailIds": [],
"unknownOperationalRailIds": [
"fednow"
]
}
}Limitations and assumptions
A scenario check does not query live rail status or execute a payment. 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 SWIFT MT202 Bank to Bank Cover Transfer Message Lookup for a related task: Financial-institution transfer messages and cover-payment variants carry different information.
Use Shared Branching Coop Network Surcharge Free Lookup for a related task: Shared branching and surcharge-free access depend on current institution and network conditions.
References
-
RTP FedNow Instant Availability Lookup — tool.io
Similar or alternative tools
- SWIFT MT202 Bank to Bank Cover Transfer Message Lookup
Financial-institution transfer messages and cover-payment variants carry different information.
- Shared Branching Coop Network Surcharge Free Lookup
Shared branching and surcharge-free access depend on current institution and network conditions.