Follow one payment
Start with a sale. Look up its price, inspect the parameters, then run Numscript to record the allocation.
Payment event
Choose the merchant and gross amount. This example is a Mexican Visa payment in MXN.
Pull the merchant’s price
Read the price effective at the event time from the shared etcd price book. This step only retrieves the price.
Review the price here, then build the parameters in step 3.
Build the Numscript parameters
Combine the event with the price from step 2. MXN amounts are passed as integer cents.
Saves the parameters for review. Ledger execution is a separate action in step 4.
| Parameter | Value passed to Numscript | Comes from |
|---|
These exact inputs are saved. Later price changes do not alter this event or its retries.
Run Numscript in Ledger
Ledger receives the saved parameters and executes the template. No transaction is posted until you run it.
Inspect the exact request and template
View recorded transaction
Run Numscript in step 4, then retrieve its recorded transaction here.
Inspect the Ledger API readback
Same event. Different merchant prices.
Create one sale for each merchant and compare the recorded fees. All five sales use the same Numscript template.
5 merchants × MXN 1,000.00Each sale looks up its own price, builds its parameters and runs in Ledger.
This creates five transactions and changes test balances every time.
Results will use the prices active when you run the comparison. No estimates are shown.
| Merchant | Applied fee | Kushki fee · MXN | Merchant gets · MXN | Transaction |
|---|
Interchange is 1.50% and scheme is 0.10%. ACME follows the September example; the other merchants are test variations. Edit a fee in Price book, then repeat to see its effect.
Merchant price book
Each record supplies the bank, entity and three fee rates used by Numscript. Each merchant’s record has its own revision within this one shared book. These are the prices effective now; a payment uses the revision effective at its event time.
| Merchant | Bank | Entity | Interchange | Scheme | Kushki fee | Merchant revision | Actions |
|---|
Read from the etcd quorum · MX / MXN / VISA. Bank and entity identify Ledger accounts. ACME follows the September example; BETA–EPSILON are test variations. This demo lets you change the Kushki fee; the other fields are stored with every revision.
Complete stored price record
Publish a new price
Numscript run history
Inspect each execution submitted through this demo, with the price and parameters it used at the time. Today’s price changes do not rewrite earlier runs.
| Run at · local time | Event / merchant | Merchant price used | Outcome | Ledger ID |
|---|
Each retry appears as a separate run attempt and can return the same Ledger transaction. Choose Inspect run to see that attempt’s time, template, saved inputs and outcome.
All saved events, including parameters awaiting execution
| Event / merchant | Merchant price | Result | Ledger ID | Actions |
|---|
Selected event
Exact request, attempts and Ledger readback
Merchant balances
Actual Ledger account volumes · MXN
| Account | Balance |
|---|
Rejected source inputs
Correct the source input and resubmit. Once an event has saved parameters, changing them requires a new event ID. A retry does not rewrite them.
Technical details
Live service health and the Numscript template.
Services
Cluster response and Ledger target
Three actual etcd members sharing one host. Quorum loss blocks price lookup and new event preparation. This does not establish independent hardware failure domains or production capacity.