> For the complete documentation index, see [llms.txt](https://docs.oripa.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oripa.xyz/mechanics/physical-cards.md).

# Physical cards

Every card in an oripa.xyz pool is a real card held in the vault until you ship or melt it. Where cards are held, how shipping works, and what happens if a card is lost.

**TL;DR:** Every card in a pool is a real card, held in the oripa.xyz vault until you ship it or melt it. Select a card for shipping within 24 hours of the rip, up to 5 cards per wallet per day. Shipping is available to Japan, South Korea, Taiwan and Hong Kong for 25 USDC per shipment.

## Where the cards are

Cards are held in the oripa.xyz vault. Each card has a serial number inside oripa.xyz that follows it from intake to shipping or melt.

## Condition

A card is sold as described on its pool page.

## Shipping

|                  |                                                                                                                                                                                 |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Request          | Select the card within 24 hours of the rip. Up to 5 cards per wallet per day.                                                                                                   |
| Regions          | Japan, South Korea, Taiwan and Hong Kong. A card that cannot be shipped to you can still be melted.                                                                             |
| Fee              | 25 USDC per shipment, charged from your balance when you confirm. Cards you select on the same day for the same address ship together for one fee. A day starts at 00:00 UTC+8. |
| Carrier          | A tracked carrier. The tracking number is sent to you when the shipment is dispatched.                                                                                          |
| Time             | Dispatched within 5 business days of your shipping confirmation. Transit time depends on the carrier and customs.                                                               |
| Duties and taxes | Paid by the recipient at the border                                                                                                                                             |

## Lost or damaged

Loss or damage in transit is covered by the carrier, and that cover is included in the shipping fee. If a card does not arrive or arrives damaged, contact support (see [About oripa.xyz](https://docs.oripa.xyz/getting-started/about.md)) with the tracking number and photos. oripa.xyz files the claim with the carrier for you. Compensation is what the carrier pays.

## Melted cards

A melted card goes back into the vault and can appear in a later pool at a new locked price.

## Address and privacy

Your shipping address is used for the shipment and shared only with the carrier. It is not written onchain.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.oripa.xyz/mechanics/physical-cards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
