Answers before your next reveal.

You need Xaman installed and an activated XRP Ledger Mainnet account with enough real XRP for the pack price and network fee. Make sure Xaman is connected to Mainnet before you connect.

Select Connect Xaman, then scan the QR code with Xaman or use the mobile handoff. Approve only the sign-in request shown by Xaman. Connecting proves control of your public wallet address; it never gives Ledgerborn access to your private keys.

Keep the Ledgerborn tab open while you approve the request in Xaman. A payment can remain pending while the XRP Ledger validates it or while the browser waits for confirmation. Do not submit a second payment immediately—first check your Xaman transaction history for a validated transaction.

An XRP Ledger Mainnet transaction cannot be reversed after validation. You can reject an unsigned request in Xaman, but always confirm that the request uses Mainnet and verify the real-XRP amount and destination before approving payment.

Each pack contains three collectible cards from the selected set. The pack page shows the available collection, price, card count, and rarity odds before you approve payment.

Pack contents are selected using the rarity odds displayed on the pack page. Each reveal is independent, so a rarity tier is never guaranteed unless the pack page explicitly says otherwise. Rarity describes scarcity, not financial value.

Yes. Pack results are independent and duplicates are possible within your wider collection. A previous pull does not remove that card from future pack results.

Cards are delivered to the XRP Ledger wallet connected when you bought the pack. After each card is minted, use its Claim NFT button to review and accept the destination-restricted offer in Xaman. A revealed card is not in your wallet until its offer has been accepted.

After flipping a card, tap Claim NFT. Ledgerborn will hand the offer to Xaman. Approve the correct NFT offer there, then return to your browser so the claim status and collection can refresh. If the handoff does not open, return to Ledgerborn and use Claim NFT again rather than paying for another pack.

Minting, metadata preparation, and offer creation are separate steps and one may be temporarily delayed. Keep the payment hash, reconnect the same wallet, and use the retry or recovery action. A retry resumes the existing paid order; it does not require another pack payment.

An expired offer cannot be accepted. Reconnect the wallet that purchased the pack and use the card claim retry or recovery panel to request a fresh eligible offer. Always confirm the destination wallet and NFT details in Xaman.

Return with the same wallet and use the recovery panel on a pack page. It can locate eligible paid orders, resume incomplete minting, and restore outstanding claim offers. Check Xaman for pending offers and refresh your wallet collection before trying another purchase.

Disconnect, confirm the active account in Xaman, and reconnect. If you use more than one Xaman account, compare the first and last characters of the address before approving any request.

Wait a moment for the current request to expire, refresh the page once, and reconnect Xaman. Disable aggressive content blockers for Ledgerborn and avoid opening multiple purchase tabs. On mobile, return to the browser after completing the Xaman request.

No. Ledgerborn only uses your public wallet address and public transaction information needed to provide the service. Never enter a private key, family seed, or recovery phrase into this site—or share it with anyone claiming to provide support.

First confirm in Xaman that the NFT offer was accepted and validated. The Collection view reads public XRP Ledger holdings and may briefly show cached results while the ledger or index updates. Reopen Collection or clear Ledgerborn site data if an older browser cache persists; this cannot remove an on-ledger NFT.

Ledgerborn may temporarily cache collection display data against your public wallet address so repeat visits load faster. Clearing browser site data removes only that local display cache. Pack delivery and NFT ownership are recorded separately in operational records and on the public XRP Ledger.

Open the transaction in Xaman and confirm that it is validated, then note its transaction hash, destination, amount, and timestamp. Public XRP Ledger explorers can also display the same on-ledger details.