API Overview

Card Present Connect | Lodging Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Card Present Connect | Lodging
- Supported Card Types
- Prerequisites
- Validation and Certification
  - Message-Level Validation
  - EMV Level 3 Certification
- Card-Present Transaction Risk Control Requirements

Lodging Transaction Scenarios
- Check-In Transaction Scenario
- Incremental Authorization Scenario
- Check-Out Transaction Scenario
- No-Show Transaction Scenario

Lodging Payment Services
- Lodging EMV and Card Data
- Lodging Transaction Descriptions
- Lodging Data Fields
- Check-in Authorization with Contact EMV and TMS Token Creation
  - Required Fields for a Check-in Authorization with Contact EMV and TMS Token Creation
  - REST Example: Check-in Authorization with Contact EMV and TMS Token Creation
- Check-in Authorization with Contact EMV PIN Debit
  - Required Fields for a Check-in Authorization with Contact EMV PIN Debit
  - REST Example: Check-in Authorization with Contact EMV PIN Debit
- Incremental Authorization
  - Required Fields for an Incremental Authorization
  - REST Example: Incremental Authorization
- Check-Out Capture
  - Required Fields for a Check-Out Capture
  - REST Example: Check-Out Capture
- No-Show Sale Using a Stored Credential
  - Required Fields for a No-Show Sale Using a Stored Credential
  - REST Example: No-Show Sale Using a Stored Credential

On This Page

No-Show Sale Using a Stored Credential

Request a no-show sale when the customer does not use or cancel the reservation. In this scenario, use the stored credential (token) to charge the customer an agreed-upon fee, as stated in your lodging's disclosed no-show and cancellation policies.

Endpoint

Production:

POST https://api.cybersource.com/pts/v2/payments

Test:

POST https://apitest.cybersource.com/pts/v2/payments

Back to top