BNB Chain · BEP-20

Payment infrastructure with a verifiable on-chain layer

Xandor Pay builds tooling for crypto payments and settlement. XDR is the utility token of that ecosystem. Everything on this page can be checked on-chain — no promises, only published data.

Total supply
1,000,000,000 XDR
Network
BNB Chain (BEP-20)
Trading pair
XDR / BSC-USDT

/ 01

About the project

What Xandor Pay is today, in plain terms.

Xandor Pay is a payment infrastructure project: accepting crypto payments, converting and settling them, and giving merchants and users a clear view of every transaction.

The problem we address is practical. Crypto payment flows are often opaque: unclear routing, unclear fees, and no simple way to verify what happened. Our approach is to keep the settlement layer on a public chain, so every step can be inspected independently.

What actually works today: the XDR token is deployed on BNB Chain, an XDR / BSC-USDT liquidity pool is live on PancakeSwap, and the contract and pool can be reviewed on BscScan and DexScreener. Further product modules are in development and will be published as they ship.

Transparency

Contract, liquidity pool and key addresses are published on this page and verifiable on BscScan.

Technology

Settlement runs on a public chain; the token follows the standard BEP-20 specification without hidden mechanics.

Real liquidity

A live XDR / BSC-USDT pool on PancakeSwap. Depth is limited at this stage and we state that openly.

Team

A small product team with direct contact channels for support and partnership questions.

/ 02

XDR Token

A utility token of the Xandor Pay ecosystem, issued on BNB Chain.

Token contract (BEP-20)

0x013D29b5BD50C975DA31EFFe894a09fc26f1c42B

Always verify the contract address before any transaction.

The XDR price is set by the market. It is not fixed, not pegged, and can move sharply in either direction.

/ 03

Tokenomics

Supply figures and the structure of allocation.

Total supply1,000,000,000 XDR
Circulating supplyNot separately published yet
NetworkBNB Chain (BEP-20)
Token symbolXDR

Allocation structure

  • Liquidity / LP

    Tokens paired in the XDR / BSC-USDT pool.

  • Treasury

    Operations, infrastructure and product development.

  • Team & Advisors

    Long-term allocation for the team and advisors.

  • Community / Marketing / Ecosystem

    Integrations, partnerships and ecosystem programs.

Exact allocation percentages are not published yet. They will be added here once finalised and verifiable.

/ 04

Vesting & Locks

What is and is not claimed at this stage.

On-chain vesting schedules and liquidity locks are not claimed on this page. If such mechanisms are introduced, their public addresses, terms and verification links will be published here.

/ 05

Treasury & Liquidity

Key addresses associated with the project.

Liquidity Pool (XDR / BSC-USDT)

PancakeSwap pair address

0x5eA4Ee6B338CC2d330302D314cc17146452983D5

The pair is on BNB Chain (BEP-20) and can be inspected on BscScan and DexScreener.

/ 06

Risks

Please read this section before interacting with the token.

  • Price volatility

    The token price can change significantly within short periods, including large drops.

  • Limited liquidity

    At this stage pool depth is low. Even relatively small trades can move the price noticeably.

  • Market capitalisation is not exit value

    A nominal market value does not mean a large amount can be sold quickly. Selling size usually results in significant slippage.

  • Smart contract and protocol risk

    Bugs or exploits in the token contract, PancakeSwap, BNB Chain or related protocols can lead to loss of funds.

  • Regulatory risk

    Rules for crypto assets differ by country and can change, which may affect access to the token or related services.

  • Operational risk

    The project is at an early stage. Roadmaps, timelines and product scope may change.

/ 07

Team & Contacts

Direct channels, no intermediaries.

The team currently works under pseudonyms and communicates through the official channels listed below. We do not have staff members writing to users first, and we never ask for seed phrases or private keys. Any message claiming otherwise is not from us.