Skip to main content

Get Started with Lodging


Prerequisites

Before integrating services for lodging transactions, you must have these items in place:

  • Merchant account with an acquirer that is enabled for processing lodging transactions on .
  • account for payment services.
  • Payment technology provider (PTP) that is integrated with and can perform message-level validation (MLV).
  • EMV Level 1 certified terminals and EMV Level 2 certified software in preparation for EMV Level 3 Certification.

Validation and Certification

Work with your payment technology provider (PTP) to allocate time to complete the message-level validation (MLV) and EMV Level 3 certification with your lodging processing system. You must pass MLV before beginning EMV Level 3 certification. You must complete validation and certification before your system can move to production. For more information, see Prerequisites.

Message-Level Validation

Message-level validation (MLV) is a script-based field-level validation against specifications.

Your PTP uses amount-based test triggers to send transactions to a test environment and the Visa Certification Management System for decryption. The test results are XML or RESTful output, test transactions, and log prints.

uses these tests to validate the results:

  • Cross-edit checks
  • Data element validation
  • Interchange compliance
  • Data mapping validation

EMV Level 3 Certification

This topic is an overview of the Level 3 certification with and . For details on how to design an EMV Level 3 certified payment application, see EMV Book 3 on the EMVCo website.

Certification is a formal process that is used to validate the device and application compliance with card scheme acceptance requirements. The certification team uses a brand test tool and simulator. The process involves these elements:

  • Using a card simulator such as ICC or Fime.
  • Failed case analysis and resolution.
  • For Mastercard certification, your PTP submits results to Mastercard and pays the costs for approved partners that Mastercard uses.
  • For Visa certification, submits results to Visa.
  • Waivers from the card schemes for exceptions.
  • Card scheme responses or Letter of Approval (LOA) to signify acceptance and Level 3 certification.

The processes and support for Global Card Present Connect projects and direct merchant and acquirer projects are different, but the timelines are essentially the same.

Get Started with the REST API

Set up your payment processing system to be REST compliant. If you have not set up secure communications between your client and server using either JSON Web Token (JWT) or HTTP signature messaging, see Getting Started with REST.

Last published: September 29, 2026