Zelle® Payment and RFP ID generation¶
Payment ID¶
Network requirements¶
Total of 12 case-sensitive alpha numeric characters. The first three are the sending org id.
PayCenter Payment ID structure¶
Note
This is the accepted structure planned for deployment 2025-01.
To ease with lookups and troubleshooting, the following pattern is used:
- Three character upper-case org id
- Nine upper-case alphanumeric characters.
Example
JB1DKLPG800
JB1DKLPG801
JB1DKLPG802
JB1DKLPG803
Components¶
[Timestamp][WorkerID][Counter]
- 6 characters for the timestamp: Covers 60 years of operation starting from an epoch date. The proposed epoch is 2025-01-01.
- 1 character for the worker ID: Supports up to 36 worker nodes.
- 2 characters for the counter: Supports up to 1,296 unique IDs per second per worker.
Note
See related ADR 13.
Payment Request ID¶
Network requirements¶
Total of 13 case-insensitive alpha numeric characters. The first three are the sending org id.
PayCenter Payment Request ID structure¶
Note
A sequenced pattern similar to the proposal for PaymentID is under consideration.
Payment Request ID:
- Three character upper-case org id
- Ten alphanumeric characters generated randomly
Example
JB4ucNXqbpbcT
JJ6PycEHSsRoJ
JB44mkzUXRZ5o