Recycled-PVC card direction
A durable card-body direction shown without cruise-line identity or compatibility marks. Final credential construction and claims require approval.





Marine hospitality / Product
Cruise cards specified for the onboard system.
A cruise credential must be defined by the supported onboard environment, intended functions, issue workflow and voyage handling requirements.
Start with your property ↗Decision framework
Confirm each supported function and credential requirement with the accountable shipboard technical process.
Then approve body material, print, variable data, packing and delivery around the sailing schedule.
Specification
| Card format | CR80, 85.6 × 54 mm |
|---|---|
| Card body thickness | 0.76 mm |
| Credential frequency | 13.56 MHz, ISO/IEC 14443 |
| Chip tiers | Entry HF, standard HF, high-security HF or AES-secure HF — tier selected from the confirmed system requirement |
| Card body material | Recycled PVC |
| Print and finish | Full-colour print with matte or gloss finish directions |
| Variable data | Numbering, cabin or voyage fields where the onboard workflow supports them |
| Minimum order quantity | 500 pieces |
| Production time | 14–21 days after artwork approval |
| Compatibility | Confirmed with the accountable shipboard technical process before production |
Figures describe the standard product platform. Chip tier, finish, closure and delivery scope are confirmed per property; compatibility is never assumed from the table alone.
Cruise card library / 05
These unbranded recycled-PVC directions illustrate card body, edge, colour, issue and production review. Shipboard support, recycled content and operating limits remain document-dependent.
Request the product brief ↗A durable card-body direction shown without cruise-line identity or compatibility marks. Final credential construction and claims require approval.





Onboard evidence, issue control and voyage timing are handled as three distinct release points.
Tie the card construction to confirmed onboard requirements.
Define encoding, numbering and guest handoff.
Build proof, production and delivery around the required-on-board date.
Start with the property, use case, destination and what is known about the installed access environment.
Three controls before release. Each stage is reviewed separately so an attractive product direction never substitutes for technical or operational confirmation.
Open the property brief ↗