Part 6: Realtime Authorisations
Introduction
This section explains how a Blockchain Network receives booking events in real time and executes custom business logic—typically booking—based on the received data.
Fiat24 sends events using webhook-based communication, where the Blockchain Network hosts an HTTP server and Fiat24 acts as the client. The reason we need such a webhook is to compensate for the fact that blockchains like Mantle cannot confirm transactions within one second, while real-time decisions are required to fulfill transactions such as card spending.
Each Blockchain Network must provide a webhook and register it with the Fiat24 backend. The webhook must strictly adhere to the following specifications. Fiat24 sends HTTP POST requests in JSON format.
Communication Format
To use the Fiat24 notification system, Blockchain Network must share the following information:
Basic authentication credentials (
username
&password
)HTTP server
URL
We strongly recommend whitelisting our IP 111.222.333.444
only.
Card Transactions
To ensure real-time processing within 1 second for critical operations like:
Swiping a card to make an authorisation, or
Increase the amount to a previous authorisation
Reversing a booking
The webhook will send the following request and expect the response within 1 second.
Processing
the field
tokenId_
need to be transformedFor Mantle network,
tokenId_ = tokenId_ - 100000000000
For BNB Chain network,
tokenId_ = tokenId_ - 200000000000
the fields
cardCurrency_
,settlementCurrency_
,originalPaidCurrency_
need to be replaced by currency contracts deployed on the blockchain network.Replace
0xbE00f3db78688d9704BCb4e0a827aea3a9Cc0D62
to your USD24 addressReplace
0xd41F1f0cf89fD239ca4c1F8E8ADA46345c86b0a4
to your CHF24 addressReplace
0x2c5d06f591D0d8cd43Ac232c2B654475a142c7DA
to your EUR24 addressReplace
0x7288Ac74d211735374A23707D1518DCbbc0144fd
to your CNH24 address
Response
Response code 200 indicates the debit request is approved.
Last updated