API and JSON in banking: what they actually do
Why an API call never touches the ledger, and why a JSON payload on its own is not proof that a payment happened.
Step-by-step guide to run Protocol 101.x and 201.x transactions on the Global Server platform.
Published
Install the Global Server desktop client from the member dashboard.
Log in to the member dashboard, then:
Open the software and enter the access code you created in the member dashboard
From the home screen/menu, tap “NEW TRANSACTION.”
This will open the guided flow for Protocol 101 or Series 201 transactions.
Use one of the available protocols (Series 101.x: 101.1, 101.2, 101.3, 101.4, 101.5 or Series 201.x: 201.1, 201.2, 201.3) according to the data on the Black Screen and Blue Screen.
Selecting the wrong protocol will cause the transaction to fail.
Enter the card number, expiration date, transaction amount, currency, and approval code according to the data displayed on the Black Screen and Blue Screen.
Ensure all data is entered accurately before proceeding.
The server will execute and process the request over the network.
Processing time depends on connection quality, ranging from a few minutes to several hours for more complex operations. Keep your Wi-Fi on and prevent the device from entering sleep mode until the process is complete.
When the process is complete, the app will display the final status, such as Approved or Failed.
You can view the details in the app or on your member dashboard.
This refers to a family of online-style transaction flows (101.1–101.5) that are executed via a server. Each variant corresponds to a different processing path.
The 201.x series is designed for offline or pre-authorization transactions. Use this protocol when the operation requires a different processing path from the standard online 101 series.
It is best to avoid this. For smooth results, keep the screen active, the app in the foreground, and Wi-Fi on until the status appears.
Install the Global Server desktop client.
In the member area, create an Access Code and Set Up Card.
NEW TRANSACTION → select 101.x or 201.x → fill out the Black/Blue Screen form with the required transaction data.
Keep the device active while the server processes.
Review the Approved/Failed results and logs.
Following these steps ensures a clean and successful transaction execution.
Why an API call never touches the ledger, and why a JSON payload on its own is not proof that a payment happened.
What L2L really means, how banks move money between ledgers in practice, and where ILP does and does not fit.
General explanations only get you so far. Bring us the specifics and you get a written answer, including the ones we turn down.
Ask a specific question