Payment Gateway Integration

Quick Setup

Set your gateway first. Then choose billing view and payment rules. Most hotels finish in 5 minutes.

This guide helps you set payment and billing display rules in Settings → Payment. If you use Stripe, choose Live or Test before connecting. Gateway Stripe credentials stay on the payment card. Terminal manual credentials stay on the terminal configuration card and use test keys only. If your hotel uses manual Stripe test credentials, gateway and terminal cards save them separately. Use the Stripe test keys for each card you configure. Room-payment waivers check reservation comments and source labels for a standalone keyword. Opera travel-agent names like Booking.com (VCC) can also trigger the same waiver. The old OTA source selector is no longer part of this page.

Where to Find It

Settings → Payment

Quick Reference

Setting Area	What It Controls	Main Outcome
Billing View	Detailed or simplified guest billing summary	Shows itemized rows or a shorter summary
Payment Gateway Integration	Stripe or Red Dot setup	Guests can pay in kiosk flows
Stripe Environment	Live or Test mode for Stripe gateway and terminal connections	Locks after connection
Manual Stripe Test Credentials	Test-only Stripe keys on the gateway and terminal cards	Saves gateway and terminal Stripe settings separately
Terminal Payment Configuration	Stripe terminal API key, publishable key, and webhook secret	Saves terminal credentials separately from gateway Stripe
Payment Collection Mode	Deposit and full payment toggles	Controls what guests pay at check-in
Comment-Based Room Payment Waivers	Waiver keyword in reservation comments	Skips empty-balance blocks when your PMS exposes keyword-waiver support
AVA Billing Rules	PMS hide and waive signals for room, tax, deposit, and incidental rows	Shows hidden rows as ✅, keeps the payable total numeric, and recalculates what you owe
Property Currency (in Settings → Essentials)	Resolved currency for deposits and reservation payment display	Keeps payment amounts consistent across settings and operations
Deposit Currency	Currency used for deposit amounts on this page	Saves with your other payment settings
Opera Payment Mapping	Settlement, cashier, and payment type mapping	Opera receives payment postings correctly
Opera Payment Policy Controls	Rounding, pre-auth, hide, and no-collect logic	Opera-specific payment behavior is enforced

Before You Start

• Prepare your payment gateway account
• Decide if you want Detailed or Simplified billing view
• Decide if you want deposits, full payment, or both
• Confirm your deposit policy and property currency source in Settings → Essentials → Hotel Basic Details
• Confirm your PMS version explicitly supports payment waiver keywords. If AVA cannot confirm support, the field stays hidden.
• If you use Opera, AVA billing rules are available there first.
• If you use Opera, prepare your cashier ID and payment method code mappings

Step-by-Step Setup

Step 1: Select a Payment Gateway

1. Go to Settings → Payment.
2. In Payment Gateway Integration, select Stripe or Red Dot Payment.

For Stripe

1. Open Advanced.
2. Choose Live or Test.
3. Click Connect Stripe.
4. Finish Stripe onboarding.
5. Return to Streamliner and confirm Stripe is connected.

Stripe mode

Use Live for production and Test for sandbox onboarding. After Stripe connects, the environment becomes read-only until you disconnect.

Terminal Stripe setup also defaults to Live unless you change it before connecting.

Manual Stripe Test Credentials

Use this when your hotel has the manual Stripe test credential fields enabled.

1. Open the Stripe card you want to edit.
2. Enter the Publishable Key, Secret Key, and Webhook Secret.
3. Use test-only keys for that card.
4. Click Save.
5. If the fields are masked later, click Save again without retyping them.

Separate Stripe cards

Gateway Stripe credentials save on the payment gateway card. Terminal Stripe credentials save on the terminal configuration card. Keep gateway and terminal keys separate.

Terminal checkout

When a kiosk has one mapped Stripe terminal, AVA opens it automatically during checkout. When more than one terminal is mapped, you choose from the terminal picker in the payment modal. If terminal mode is off, AVA keeps the gateway or QR payment flow. If the kiosk uses direct Stripe Terminal credentials, AVA can still start checkout even when Stripe Account ID is blank. When both direct credentials and a Connect account exist, AVA keeps the Connect account behavior. Terminal manual credentials are separate from gateway Stripe credentials. Use them only for test terminals. If the fields are masked, you can save them again without retyping the values.

For Red Dot Payment

1. Enter Merchant ID.
2. Enter Secret Key.
3. Select Environment (TEST or LIVE).
4. Click Save Payment Gateway Settings.

Step 2: Choose Billing View

Use this card to control the guest-facing billing summary. Choose Detailed for itemized rows. Choose Simplified for Room Charges, Tax, and the total.

1. Go to Settings → Payment.
2. In Billing View, choose Detailed or Simplified.
3. Click Save.

Billing view placement

This card appears before Terminal Payment Configuration on the payment page.

Step 3: Choose Payment Collection Options

Toggle	What It Does
Collect Security Deposits	Pre-authorizes a deposit during check-in
Collect Full Payment	Guests pay outstanding balance during check-in

1. Turn on one or both toggles.
2. If both are off, check-in does not request payment.
3. Click Save Payment Gateway Settings.

Step 4: Configure Deposit Details (If Enabled)

1. Enter Deposit Amount.
2. Choose Deposit Type (per night or flat amount).
3. If you see Deposit Currency, choose the currency your hotel uses for deposits.
4. Click Save Payment Gateway Settings.

Deposit currency source

Payment settings use the resolved Property Currency from Settings → Essentials → Hotel Basic Details. If PMS provides currency, AVA uses that value and locks local edits. Your selected Deposit Currency saves with the rest of your payment settings.

Comment-Based Room Payment Waivers

Use this when AVA should skip room payment from a supported PMS keyword waiver.

• Set one waiver keyword in Payment Policy Controls.
• AVA checks reservation comments and source labels for that keyword.
• Opera also passes travel-agent profile names into the same match.
• If the keyword matches as its own word, AVA skips the payment block.
• If it only appears inside a larger token, AVA keeps the balance payable.
• If it does not match, AVA still treats the balance as payable.

Opera source labels

If Opera returns a travel-agent label, AVA can read values like Booking.com (VCC). That label may satisfy the waiver keyword.

Universal waiver behavior

When AVA cannot confirm keyword-waiver support, the editor stays hidden. Cloudbeds, eZee, Ava, Furama, unknown vendors, and unsupported PMS versions do not show the field.

1. Open Payment Policy Controls.
2. Enter the waiver keyword your PMS writes into reservation comments.
3. Click Save.
4. Test with a reservation that includes the keyword.

AVA Billing Rules

Use this when your PMS sends hide or waive signals for room, tax, deposit, or incidental rows.

• Opera is the first PMS with this support.
• Hidden room or tax rows show as ✅ in detailed billing.
• Waived room or tax rows stay visible, but AVA recalculates the amount due.
• Waived deposit or incidental rows are removed from the payable total.
• Simplified billing shows hidden room and tax rows, an Extras separator, and grouped extra items by code.

Capability-gated rollout

If your PMS does not support AVA billing rules, AVA keeps the normal payment summary.

1. Open a reservation that uses the PMS billing rule.
2. Refresh the reservation in AVA.
3. Compare the visible rows with the payable balance.
4. Test again after the PMS sync completes.

Step 5: Configure Opera Payment Mapping (Opera Only)

1. In Opera PMS Payment Mapping, set:
   • Settlement Code
   • Default Cashier ID
   • Default Comment Type / Location
   • Payment Type to Payment Method Code rows
2. Click Save Opera Payment Mapping.

How mapping rows work

Each row links one payment method to one OPERA payment method code. AVA saves these rows with your other payment settings.

Opera payment comment defaults

AVA sends your configured Default Comment Type / Location when it creates Opera payment or deposit comments. Save the mapping again after changing this value.

Step 6: Configure Opera Payment Policy Controls (Opera Only)

1. In Opera Payment Policy Controls, set payment behavior:
   • Invoice visibility and checkout verification
   • Rounding adjustment and transaction code
   • Auto delay capture options
   • Hide and no-collect rule lists
2. Click Save Payment Policies.

Opera payment comments

AVA tries to add the Opera reservation comment before it posts the payment or deposit. If comment creation fails, AVA still posts the payment or deposit in Streamliner. This keeps payment collection moving even when Opera comment creation fails. The universal room-waiver keyword is configured above.

What to Expect After Save

• ✅ Connected gateway details appear after setup
• ✅ Stripe shows Live or Test in the connected status badge
• ✅ Billing view saves with the rest of the payment settings
• ✅ Deposit fields appear when deposits are enabled
• ✅ Deposit currency stays saved after you click Save
• ✅ Opera mapping and Opera policy sections appear only for Opera PMS
• ✅ The Step 3: Configure Opera PMS Payment Mapping card appears when active PMS provider is Opera
• ✅ Payment settings save independently on the same page

Migration Note

Payment setup moved from Settings → Essentials to Settings → Payment. Legacy OTA source selectors were removed.

Troubleshooting

Gateway settings are disabled

What you see: Payment toggles or save buttons are disabled.

Fix:

1. Confirm your account has settings write access.
2. Connect Stripe first if Stripe is selected.
3. Refresh the page and retry.

Billing view does not change

What you see: Guests still see the old billing summary layout.

Fix:

1. Return to Settings → Payment.
2. Re-select Detailed or Simplified.
3. Click Save on the Billing View card.
4. Start a new guest flow or refresh the reservation screen.
5. If it still looks wrong, confirm the hotel is on the current CCI settings path.

Stripe environment is locked

What you see: The Environment dropdown is disabled after Stripe connects.

Fix:

1. Disconnect Stripe.
2. Open Advanced.
3. Choose Live or Test.
4. Reconnect Stripe.

Stripe terminal credentials are rejected

What you see: Gateway or terminal Stripe credentials do not save, or AVA clears them after you save.

Fix:

1. Confirm you are editing the right Stripe card.
2. Gateway and terminal credentials save separately.
3. Use test-only values for manual Stripe setup.
4. Make sure the secret key starts with sk_test_.
5. Make sure the publishable key starts with pk_test_.
6. Save the settings again.
7. If the fields are masked, save again without retyping the values.

Stripe test credentials do not appear

What you see: The manual Stripe fields are missing from the gateway or terminal cards.

Fix:

1. Refresh Settings → Payment.
2. Confirm your hotel is in the manual Stripe test credential rollout.
3. Contact support if the fields still do not appear.

Opera sections do not appear

What you see: Opera mapping and policy cards are missing.

Fix:

1. Open Settings → Essentials → PMS Integration.
2. Confirm PMS provider is Opera.
3. Return to Settings → Payment.
4. Refresh the page once.
5. Check that Step 3: Configure Opera PMS Payment Mapping appears.

Opera payment mappings do not save

What you see: Your cashier or payment method rows disappear after you click Save.

Fix:

1. Open Settings → Essentials → PMS Integration.
2. Confirm Opera is still the active PMS.
3. Return to Settings → Payment.
4. Re-enter Default Cashier ID and each mapping row.
5. Click Save Opera Payment Mapping again.

Opera reservation comment is missing

What you see: The payment posts successfully, but you do not see a new reservation comment in Opera.

Fix:

1. Confirm the payment or deposit finished successfully in Streamliner.
2. Check that the Opera reservation has a matching payment record.
3. Confirm Default Comment Type / Location is set in Opera PMS Payment Mapping.
4. Do not retry only to recreate the comment.
5. Contact support if the payment posts and the comment still does not appear.

Opera comment type or location looks wrong

What you see: Opera creates the payment comment, but the type or location looks unexpected.

Fix:

1. Open Settings → Payment.
2. Check Opera PMS Payment Mapping.
3. Verify Default Comment Type / Location.
4. Save the mapping again.
5. Test another Opera payment or deposit.

Room payment is waived unexpectedly

What you see: A reservation skips room payment when you expect a payment request.

Fix:

1. Open the reservation in your PMS.
2. Check the reservation comment, source name, and Opera travel-agent label.
3. Remove or change the keyword if the reservation should not be waived.
4. Refresh AVA and test again with a new reservation.

Payment waiver keyword field is missing

What you see: You do not see the waiver keyword field, or you see an unsupported PMS message in Payment Policy Controls.

Fix:

1. Confirm your PMS provider supports keyword waivers.
2. Refresh Settings → Payment.
3. If the field still does not appear, AVA does not have support data for that PMS yet.
4. Keep any existing waiver keywords in place. AVA still stores them even when the editor is hidden.

Billing rows do not match the PMS

What you see: Room, tax, deposit, or incidental rows look different in AVA.

Fix:

1. Confirm the reservation comes from a PMS that supports AVA billing rules.
2. If you use Opera, wait for the next reservation sync.
3. Refresh Settings → Payment or reopen the reservation.
4. Check the PMS bill to confirm whether the row is hidden or waived.

Guests are not asked to pay

What you see: Guest skips payment during check-in.

Fix:

1. Confirm a gateway is connected.
2. Confirm Collect Security Deposits or Collect Full Payment is enabled.
3. Confirm the reservation has a balance due.
4. Save and retest with a sample reservation.

Deposit currency looks wrong or cannot be edited

What you see: Deposit currency does not match your expected setting, or field changes do not persist.

Fix:

1. Open Settings → Essentials → Hotel Basic Details.
2. Check whether Property Currency is PMS-managed or editable.
3. If PMS-managed, update currency in PMS and wait for sync.
4. Refresh Settings → Payment and verify the currency.

Related Settings

• Check-In Policy
• PMS Connection
• Opera PMS Integration

Still Stuck?

Contact success@vouch-technologies.com if:

• ❌ Payments still fail after re-saving settings
• ❌ Billing view changes do not appear for guests
• ❌ Opera mapping values do not persist
• ❌ Stripe or Red Dot connection repeatedly disconnects

Helpful to include:

• Screenshot of Settings → Payment
• PMS provider name
• Example reservation ID and timestamp