VERTICAL · Hospitality

Build for
Hospitality

Check-in auth, incremental charges, no-show fees, and multi-property tokenization — the full lodging payment stack.

-5 days to first transaction
Get Sandbox →
Build with AI
Fitness illustration
module icon
MODULE
SMB & Enterprise
integration model icon
INTEGRATION MODEL
Embedded / Card Present
channels icon
CHANNELS
CP, CNP
time to build icon
TIME TO BUILD
~5 days
use case

Typical use cases

Three patterns we've seen ISVs implement most often.

Property management system

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

  

Online booking platform

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

  

Multi-property hotel chain

Centralized token vault for card-on-file across 100+ properties — check in once, charge everywhere.
use case

Required stack

What you'll wire up. Click any tile to see why it's in the recipe.

Core · Always required
 

Accept Payments

Authorize and capture transactions across CP and CNP channels.

required
APISDK
  

Tokenization Service (TMS)

Token vault for card-on-file across properties — check-in once, charge throughout stay.

required
APISDK
  

Unified Checkout

Hosted UI for online reservation payment capture.

recommended
HOSTED NO-CODE
Hospitality-specific · The lodging stack
 

Lodging Incremental Auth

Increase the authorized amount mid-stay for room service, minibar, spa charges.

required
API
  

No-Show Sale

Charge guest's stored credential when they fail to cancel by policy deadline.

required
API
  

Check-Out Capture

Settle the final folio amount — base rate plus all incremental charges.

required
API
Optional extensions
 

Account Updater

Auto-refresh expired cards before arrival to prevent failed settlement.

optional
API
  

Decision Manager

Fraud scoring for CNP reservations — enterprise and OTA channels.

optional
API
  

Reporting & Transaction Search

Per-property settlement reports and dispute management.

optional
API

Multi-Currency Pricing

Settle in property's currency, display in guest's local currency.

optional
API
  
use case

APIs

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

Common · All recipes
 
API REQUIRED DESCRIPTION DOCS
Payment Authorization
required
Authorize transactions across CP and CNP channels. Docs ↗
Refund & Void
required
Process refunds, voids, and reversals including check-out adjustments. Docs ↗
Lodging-specific APIs
 

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

API REQUIRED DESCRIPTION DOCS
Lodging Check-In Auth (CP)
required
EMV contact auth at check-in with TOKEN_CREATE and industryDataType=lodging. Creates customer + paymentInstrument + instrumentIdentifier tokens. Docs ↗
Lodging Incremental Auth
required
PATCH /pts/v2/payments/{id} — increases authorization mid-stay for room service, minibar, spa. Max 100 incremental auths per transaction. Docs ↗
Check-Out Capture
required
POST /pts/v2/payments/{id}/captures — settles full folio with checkInDate, checkOutDate, specialProgramCode=1. Docs ↗
No-Show Sale (Stored Credential)
required
MIT sale using stored credential. processingInformation.authorizationOptions.initiator.merchantInitiatedTransaction.reason=4. Docs ↗
Tokenization Service
required
Multi-property token vault. Single card tokenized at first stay, reused across all properties. Docs ↗
Optional
 
API REQUIRED DESCRIPTION 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 ↗
use case

Vertical insights

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

Europe
  • SCA exemptions for merchant-initiated recurring transactions
  • SEPA as alternative to card-on-file recurring
  • Consumer protection requires easy cancellation (EU UCPD)
  • VAT on fitness services varies (exempt in some markets)
Asia-Pacific
  • Multi-gym chain models span ASEAN — multi-currency required
  • UPI Autopay for recurring in India
  • ClassPass-style aggregator models dominant in urban APAC
  • Mobile-first booking — payment must be seamless in-app
Latin America
  • Credit card installments needed for annual membership pre-pay
  • PIX gaining ground for gym payments in Brazil
  • High churn — Account Updater + retry logic critical
  • Informal fitness sector — simplified onboarding needed
Middle East & Africa
  • Gender-segregated facilities — multi-location with distinct branding
  • Ramadan / seasonal billing adjustments needed
  • Premium fitness market growing in Gulf states
  • Corporate wellness programs driving B2B billing
use case

Integration path

Five steps from sandbox to live veterinary practices.

Sandbox

Register, get test credentials, configure profiles.

Develop

Build with SDKs and APIs for your channels.

Test

Execute scenarios, validate flows, confirm compliance.

Go Live

Launch with pilots, monitor, scale across portfolio.

Onboard

Onboard merchants — KYC, bank, product activation.

use case

Other recipes you might combine

Many veterinary platforms also build for these adjacent verticals.

Retail

Sell merch in-club, retail POS for accessories.
 

Hospitality

Spa packages, yoga retreats, wellness hotels.
 

Marketplace

Multi-vendor: trainers, nutrition, gear retailers.

Build faster with AI

Developer MCP

Use natural language to generate integration code, explore APIs, and debug your implementation. The Visa Acceptance Developer MCP connects your AI coding assistant directly to our documentation and sandbox.

Explore Developer MCP