Skip to main content

Flicp / Network

Ledger routing

Flicp uses the issuer's country to choose how supported coupon activity is recorded. This is an internal setup choice, not a promise about where data is stored.

01Section

How routing works

Flicp uses the issuing brand's country when setting up the coupon record. The customer's location does not change how that coupon is recorded.

02Section

What is configured today

The backend has India and global Besu connection settings. India inherits the global connection by default and can be configured with its own RPC endpoint and contract. Other mapped countries currently use the global connection. These settings alone do not confirm where infrastructure is physically hosted.

03Section

Why this matters

Keeping this setup consistent helps Flicp manage different deployments. Availability and data-storage commitments depend on the infrastructure and agreements for each deployment.

—Related

Where to go next

Coupon Rules
/network/protocols
Country settings
/network/sovereigns
Activity Record
/network/ledger