01 / SOLUTIONS

Where this recipe fits

Three patterns we've seen ISVs implement most often.

01   Property management system
Single-property to multi-location hotels — check-in auth, room service incremental charges, no-show fee collection.

02   Online booking platform
Reserve-now-pay-later flows with tokenized card capture at booking and no-show fee enforcement.

03   Multi-property hotel chain
Centralized token vault for card-on-file across 100+ properties — check in once, charge everywhere.

02 / CAPABILITIES

The payment stack

What you'll wire up. The products and capabilities in this recipe.

Accept Payments   required · API / SDK
Authorize and capture transactions across CP and CNP channels.

Tokenization Service (TMS)   required · API / SDK
Token vault for card-on-file across properties — check-in once, charge throughout stay.

Unified Checkout   recommended · HOSTED / NO-CODE
Hosted UI for online reservation payment capture.

Lodging Incremental Auth   required · API
Increase the authorized amount mid-stay for room service, minibar, spa charges.

No-Show Sale   required · API
Charge guest's stored credential when they fail to cancel by policy deadline.

Check-Out Capture   required · API
Settle the final folio amount — base rate plus all incremental charges.

Account Updater   optional · API
Auto-refresh expired cards before arrival to prevent failed settlement.

Decision Manager   optional · API
Fraud scoring for CNP reservations — enterprise and OTA channels.

Reporting & Transaction Search   optional · API
Per-property settlement reports and dispute management.

Multi-Currency Pricing   optional · API
Settle in property's currency, display in guest's local currency.

03 / BUILD

API reference

Reference for every API in the stack, grouped by integration concern.

Payment Authorization   required
Authorize transactions across CP and CNP channels.

Refund & Void   required
Process refunds, voids, and reversals including check-out adjustments.

All lodging transactions must include industryDataType=lodging in processingInformation per CyberSource lodging requirements.

Lodging Check-In Auth (CP)   required
EMV contact auth at check-in with TOKEN_CREATE and industryDataType=lodging. Creates customer + paymentInstrument + instrumentIdentifier tokens.

Lodging Incremental Auth   required
PATCH /pts/v2/payments/{id} — increases authorization mid-stay for room service, minibar, spa. Max 100 incremental auths per transaction.

Check-Out Capture   required
POST /pts/v2/payments/{id}/captures — settles full folio with checkInDate, checkOutDate, specialProgramCode=1.

No-Show Sale (Stored Credential)   required
MIT sale using stored credential. processingInformation.authorizationOptions.
initiator.merchantInitiatedTransaction.
reason=4.

Tokenization Service   required
Multi-property token vault. Single card tokenized at first stay, reused across all properties.   Docs ↗

Unified Checkout   recommended
Hosted UI with card capture, digital wallets, 3DS. Reduces PCI scope to SAQ-A.   Docs ↗

Flex Microform v2   alternative
Tokenized card fields with full UI control. ISV manages downstream transaction flow.   Docs ↗

04 / CONSIDERATIONS

Regional insights

What's different about Hospitality — surface the constraints before you architect.