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 rules in Settings → Payment. Checkout rounding is configured only on this page. The Check-In page and Assisted Check-In Setup wizard do not contain rounding controls. 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. Accommodation charge policies match values supplied by your PMS. Opera travel-agent names like Booking.com (VCC) can also trigger a matching waiver. For Opera room-package waivers, AVA waives room charge, room service charge, and room GST first. For pre-arrival Opera projections, the projected room charge and its rate-info tax are waived together. Separately posted extras and their taxes stay payable. For Mews, verified products included in a matched rate, such as bundled breakfast, can follow an accommodation waiver. Mews rate-group rules apply only to products included by the booked rate group. Products assigned to another rate group remain payable. After that waiver, AVA suppresses a positive THB 0.01 balance only when it is an accommodation rounding residual. Genuine extras and unclassified charges remain payable, including genuine THB 0.01 extras. 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 room-payment choices	Controls what guests pay during check-in and Pre-arrival
ACI payment switch	Whether assisted check-in staff can request payment	Allows or skips payment during ACI only
Pre-arrival online payments	Room and deposit switches, email timing, and pre-auth scenarios	Controls eligible online payments before arrival
Accommodation Charge Policies	Matching values that waive or hide accommodation charges	Controls accommodation rows and the payable amount when your PMS supports the capability
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 preserves payable extras
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
PMS Payment Mapping	Property-specific payment method mapping when your PMS supports it	Your PMS records captured payments under the intended category
Checkout Rounding Adjustment	Small-balance tolerance and checkout adjustment	Supported PMS providers can complete checkout with a small balance
Pre-Authorization Controls	Delayed room-rate capture from Stripe pre-authorizations	Appears when your active PMS supports delayed capture
Opera-Specific Payment Controls	Check-out verification, routing, and no-collect logic	Opera-specific payment behavior is enforced
No Post Controls	Controls OPERA posting restrictions by journey and deposit policy	Applies the priority rules described below

Rounding dependency

Rounding adjustment only works when either Check-in outstanding-balance blocking or Checkout balance settlement is on in Check-In Policy. If both are off, AVA keeps your saved rounding value, but the control stays inactive. AVA shows the control only when your active PMS reports checkout-rounding support. Missing or malformed capability data keeps the control hidden.

Capability-based controls

AVA reads checkout-rounding support from your active PMS capability. It shows Transaction Code (Rounding) only when that capability declares a vendor-code field. Unsupported or unverified PMS capabilities send no new rounding settings.

PMS terminal availability

AVA shows the PMS terminal option only when your active PMS capability supports it. For the legacy ows provider, AVA does not offer the OPI option. Existing supported PMS terminal settings continue to work.

Understand OPERA No Post for v4 journeys

Quick Setup

For v4 journeys, AVA checks the payment policy first, then the matching No Post toggle. This takes about 2 minutes to review.

AVA applies No Post using the first matching rule below.

Priority	When it applies	Result
1	Authenticated Assisted Check-In	Staff choice decides when two-device ACI supports it. Otherwise, the saved default decides.
2	Kiosk or eligible Pre-arrival with payments on and Do not collect or a 0 deposit	No Post, regardless of the toggles
3	Kiosk with payments on and a required deposit	Set No Post after Payment decides; when on, every kiosk guest receives No Post
4	Kiosk with payments off	Set No Post after Payment decides
5	Pre-arrival with a required deposit or without payments	Follow the configured payment policy

For Assisted Check-In, AVA checks the authenticated staff-device decision before deposit rules. A forged ACI header cannot bypass the guest policy. The choice applies to every reservation that the PMS checks in during that action. This includes the main reservation and newly checked-in sharers. The choice does not re-restrict reservations that were already in the room. An ACI repair follows the ACI setting; a kiosk repair follows the kiosk rules. Older v2 behavior is unchanged.

When Set No Post after Payment is off, a kiosk guest receives No Post only when the required deposit was not collected. With payments off, Set No Post after Payment alone decides the kiosk outcome.

Choose the No Post settings

1. Go to Settings → Payment.

2. Open Opera-Specific Payment Controls.

3. Keep Set No Post after Payment on when every eligible kiosk guest should receive No Post.

4. Use Tick No Post by default on Assisted Check-In to preselect the staff choice.

5. Review Deposit Collection and Do not collect because these can take priority.

6. Click Save Payment Policies.

   ✓ AVA uses the saved settings on the next eligible journey.

When a setting is hidden

AVA hides Set No Post after Payment when payments are on and Do not collect is selected. The top-priority rule already forces No Post in that case. AVA keeps Tick No Post by default on Assisted Check-In available for ACI policy.

Let two-device ACI staff decide

When OPERA reports support, a verified two-device staff kiosk shows Set No Post in the PMS above Proceed to Check-In. The saved setting preselects this box. Staff can select or clear it before check-in.

The staff choice is final for that ACI action. It applies to every reservation that OPERA checks in during the action. For an atomic multi-room check-in, all room cards share one choice. Deposit settings do not override this ACI choice.

The box is not shown on a one-device staff kiosk or the guest tablet. Those flows use the saved setting. Older staff builds also continue using the saved setting.

Kiosk sharers

Self-service kiosk check-in applies No Post to reservations newly put in house by that action. A later companion arrival receives No Post only on the companion's new reservation. AVA does not re-restrict the room's booking when a later guest joins.

No Post is a follow-up

OPERA check-in can succeed even when the No Post update fails. Verify the reservation in OPERA and apply the restriction manually when needed. AVA also skips the request when the PMS does not declare No Post support.

No Post is not available

What you see: The No Post box is missing, or the result differs from your saved default.

Fix:

1. Open Settings → Essentials → PMS Integration.
2. Confirm that Opera is the active PMS.
3. Refresh Settings → Payment.
4. Check whether payments are on and Do not collect is selected.
5. For ACI, confirm you are using a verified two-device staff kiosk.
6. Review the journey type and matching No Post setting.
7. Contact support if Opera is active but the priority behavior is incorrect.

AVA hides Set No Post after Payment when the top-priority rule always applies. It also hides Opera controls when the PMS capability is unavailable or unverified.

Before You Start

• Prepare your payment gateway account
• Decide if you want Detailed or Simplified billing view
• Decide if you want deposits, room payment, or both during check-in
• Confirm your deposit policy and property currency source in Settings → Essentials → Hotel Basic Details
• Confirm your PMS exposes the accommodation payment-policy capability. If AVA cannot confirm support, the controls stay hidden.
• Confirm your PMS exposes delayed pre-authorization capture support if you need Auto Delay Capture.
• If you use Opera, AVA billing rules are available there first.
• If your PMS supports payment mapping, 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. Manual Stripe gateway saves require Test mode and all three credential fields. You must provide the Publishable Key, Secret Key, and Webhook Secret together.

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.

Complete test credentials only

AVA rejects incomplete manual gateway saves. It keeps your existing credentials when a save is rejected. For masked fields, leave the masked values unchanged when saving.

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.

Assisted Check-In payment requests

In Assisted Check-In, staff can request the deposit, the room payment, or both for each room. Both are selected by default when the room has payment due. Staff can clear either item before requesting payment. Rooms with no payment due continue without a payment step. The Let assisted check-in staff collect payments switch must also be on. It is on by default and does not affect Self Check-In or Pre-arrival.

For one-device ACI, the payment request appears after staff select Check-in. The device returns to staff first, then the guest completes payment. For two-device ACI, staff send payment as a PAYMENT step to the guest tablet. If staff send no payment items, the guest tablet does not require payment.

When both an online gateway and a card reader are available, the guest chooses Pay online or Pay with Card Reader. The online option shows a QR code. The card-reader option uses the terminal selected by staff.

ACI payment selection is per room

Review each room's requested items before starting payment. AVA does not require an item that staff cleared for that room.

Turn off Assisted Check-In payment requests

Use this setting when your hotel collects ACI payments outside AVA.

1. Go to Settings → Check-In → Check-In Policy → Kiosk & payments.

2. Turn off Let assisted check-in staff collect payments.

3. Select Save.

   ✓ ACI no longer treats rooms as owing payment. ✓ One-device ACI continues directly to check-in. ✓ Two-device ACI does not offer a PAYMENT step.

The setting is on by default. It affects Assisted Check-In only. Self Check-In and Pre-arrival payment rules stay unchanged.

When the change takes effect

Kiosks load the change at the next Welcome page, new journey, or reload. An open tablet payment can finish, or staff can skip it.

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.

Choose Pre-authorization hold before entering the amount. The amount must be greater than 0 when this option is enabled. To skip security deposits, choose Do not collect instead.

Default for hotels without a saved deposit mode

If your hotel never saved this setting, AVA shows Do not collect. Choose another mode and save it when your property requires a deposit.

Zero amounts do not enable deposits

AVA rejects an empty or zero Deposit Amount when Pre-authorization hold is selected. The inline message explains the error and offers Switch to "Do not collect" instead.

Gateway connection requirement

AVA disables Pre-authorization hold and Deposit Amount until a payment gateway connects. Do not collect remains available so you can clear an invalid deposit configuration.

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.

Payment value checks

AVA checks payment values before saving them. Use the formats below when a field is editable.

Setting	Accepted value
Deposit Currency	Three uppercase letters, such as USD or THB
Rounding Threshold	A number of 0 or higher
Transaction Code (Rounding)	A whole number of 0 or higher
Auto Delay Capture Expiry Days	A whole number of 0 or higher

Configure Accommodation Charge Policies

Use these controls when your PMS supports accommodation payment policies. They appear under Payment Policy Controls on Settings → Payment.

Control	What it does
Waive Accommodation Charges	Does not collect accommodation charges, related taxes, or service charges. These rows remain visible.
Hide and Waive Accommodation Charges	Hides and does not collect accommodation charges, related taxes, or service charges.

Separately posted extras and their taxes remain visible and payable under either policy. If both policies match, the hide policy changes visibility only. The payable amount stays the same.

1. Go to Settings → Payment.
2. Find Payment Policy Controls → Accommodation Charge Policies.
3. Add each matching value from your PMS to the appropriate list.
4. Click Save Payment Policies.
5. Test a reservation that matches the configured value.

Capability-based visibility

AVA shows these controls only when the active PMS exposes the required capability. Existing values remain stored when the controls are temporarily unavailable.

Opera source labels

If Opera returns a travel-agent label, AVA can match values such as Booking.com (VCC).

AVA Billing Rules

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

• Mews and Opera support these rules when their connection capabilities allow them.
• Hidden room or tax rows show as ✅ in detailed billing.
• Waived room or tax rows stay visible when the provider returns them.
• A Mews v2 waive policy can clear the full invoice's charge rows.
• Verified Mews rate-included products, such as bundled breakfast, can follow a room-package waiver.
• Mews rate-group rules apply only to products included by the booked rate group.
• Products assigned to another rate group remain payable.
• Service charges priced relative to verified included products can follow that waiver.
• A positive Mews balance up to THB 0.01 is suppressed only when it is an accommodation rounding residual after a waiver.
• Positive unclassified charges and genuine extras remain payable, including genuine THB 0.01 extras.
• For Opera room-package waivers, AVA waives room charge, room service charge, and room GST first.
• Pre-arrival projected Opera room charges and their rate-info tax are waived together.
• Separately posted Opera extras and their taxes can stay payable.
• Waived deposit or incidental rows are removed from the payable total.
• An evaluated payable amount controls the balance shown and collected during checkout.
• If billing is not evaluated for another reason, AVA may use the PMS summary or stored snapshot.
• A Mews inconclusive waiver does not use an unverified amount; staff must review the complete invoice.
• When room payment collection is enabled, AVA can route the guest to the front desk during reservation lookup.
• If AVA cannot prove a product classification, it withholds the unverified amount for staff review.
• An explicit Opera zero balance stays zero, even when visible room, tax, or service postings look positive. This applies when routed or settled counterparts are not visible. AVA trusts that zero only when the amount and currency match the normalized Opera bill. A mismatch remains unconfirmed.
• Simplified billing shows hidden room and tax rows, an Extras separator, and grouped extra items by code.
• Projected billing rows can remain visible while the PMS finishes syncing.
• Compare unexpected balances with the PMS before collecting payment.
• When no policy matches, AVA uses the billing response it receives.

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.

Configure Pre-arrival Online Payments

Use this card to let eligible guests pay online before arrival. Find it at Settings → Payment → Pre-arrival online payments. The card appears after Billing View and after the payment collection settings. Configure the pre-arrival long-stay rule in Settings → Check-In → Check-In Policy.

Setting	What it controls	Requirement
Enable pre-arrival room payment	Collects the live room balance before arrival	Room collection must be Pre-authorization hold or Direct sale charge
Enable pre-arrival deposit payment	Requests the configured deposit pre-authorization before arrival	Deposit collection must be Pre-authorization hold
Pre-auth validity (days)	How long the bank keeps a pre-authorization valid	Enter 1 to 365 days

1. Open Settings → Payment → Pre-arrival online payments.

2. Turn on the room-payment switch, deposit-payment switch, or both.

3. Enter Pre-auth validity (days) when you collect a deposit.

4. Review the first scheduled email and its send time.

5. Review the Pre-auth scenarios table.

6. Click Save.

   ✓ AVA saves separate room and deposit choices. ✓ Guests see current room and deposit amounts during Pre-arrival.

Choose room payments carefully

Enable room payments when your PMS identifies OTA-paid reservations or provides suitable rate plans. This helps prevent guests from paying a room balance already collected by an OTA.

Collection modes control the switches

AVA disables and clears the room switch when room collection is Do not collect. It disables and clears the deposit switch when deposit collection is not Pre-authorization hold.

When AVA requests a pre-authorization

AVA requests a pre-authorization only when the payment invitation and stay fit within its validity. The days before arrival plus stay nights must be less than the validity period. AVA skips the request when the dates equal the expiry boundary.

Understand Room Payment Timing

The current page does not provide separate direct-sale timing controls. Room-payment invitations follow your scheduled pre-arrival emails.

1. Open Settings → Payment → Pre-arrival online payments.

2. Check the first scheduled email and send time.

3. Click Configure to adjust the schedule in Pre-arrival Emails.

4. Review every scheduled email in the scenario table.

   ✓ AVA uses the scheduled email flow for eligible room and deposit invitations.

Pre-authorization timing

Pre-arrival payment switches are off by default. The default Pre-auth validity (days) value is 7. AVA requests a pre-authorization when the email timing and stay length fit within that validity.

Payment types and exclusions

Pre-arrival payments use supported online gateways. Pre-arrival can combine eligible selected rooms into one online payment quote. AVA rechecks each selected room when it generates the payment. Terminal and cash payment methods remain excluded. QR and terminal payment generation is rejected for Pre-arrival. The selected Detailed or Simplified billing view controls the deposit summary. Direct-sale room payments follow Room collection when enabled. Deposit payments still follow the pre-authorization validity rule.

Read the pre-authorization scenarios

The table shows one to ten nights for each scheduled pre-arrival email. It helps you see whether the bank hold remains valid at that email.

Table column	Meaning
Nights	Length of the guest's stay, from 1 to 10 nights
Days to checkout	Scheduled email days before arrival plus stay nights
Request pre-auth?	Whether the hold fits within your validity setting

AVA shows ✅ when the total is less than Pre-auth validity (days). It shows ❌ when the total reaches or exceeds the validity boundary. Each scheduled email gets its own result when you use multiple emails.

For example, a first email sent 5 days before arrival and a 2-night stay gives 7 days. With a validity of 8 days, AVA shows ✅ for that scenario.

No email schedule

If pre-arrival email scheduling is unavailable or disabled, the card cannot estimate the first invitation. Open Configure beside the email message to set a schedule.

Long-stay blocking disables these switches

If Pre-arrival → Block long-stay reservations is enabled, AVA disables both switches. AVA also clears the saved pre-arrival payment choices. Turn off that rule before enabling Pre-arrival online payments.

Pre-arrival payment settings are unavailable

What you see: A switch is disabled or the card says collection is unavailable.

Fix:

1. Confirm your gateway is connected in Settings → Payment.
2. Set room collection to Pre-authorization hold or Direct sale charge before enabling room payment.
3. Set deposit collection to Pre-authorization hold before enabling deposit payment.
4. Open Settings → Check-In → Check-In Policy.
5. Turn off Pre-arrival → Block long-stay reservations, if appropriate.
6. Return to Settings → Payment and save again.

Existing paid payments

AVA accepts an existing paid state. It does not request a second payment when the relevant room or deposit payment is already complete.

Step 5: Configure PMS Payment Mapping (When Supported)

For Opera, set these fields in Opera PMS Payment Mapping:

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

AVA reads these choices from your active Opera property. AVA caches each list separately across instances for up to 30 days. Click Refresh from OPERA when you need the latest codes. Refreshing a list updates every matching picker, including fields on other settings pages.

How mapping rows work

Each row links one AVA payment method to one Opera payment method code. AVA shows active Opera payment methods in a dropdown. The list includes each method's description, card type, and transaction code. You do not need to maintain a separate list of Opera payment methods. AVA saves these rows with your other payment settings.

Opera code lists

Settlement Code uses an Opera transaction code. Default Cashier ID uses an active cashier from your Opera property. Payment method rows accept active Opera payment methods only. Reservation note settings use separate Opera comment-type and location lists. Each list loads separately, so one unavailable list does not hide the others. If a list is unavailable, AVA keeps other lists available. Fields using the unavailable list remain editable for manual entry.

Stale mapping recovery

For Opera card payments, AVA first reads the authoritative Vouch Core mapping. This makes a mapping saved moments earlier available before payment posting. If Core is temporarily unavailable, AVA can use a valid recent local mapping. If AVA still cannot find a usable Opera mapping, it refreshes the configuration once. AVA retries the payment only when no Opera payment request was sent.

Check saved codes

AVA keeps a saved code that Opera no longer provides, but flags it as unavailable. Payments using that code will not post to Opera. Replace the flagged code with an active choice before taking payments.

Older web-be-pms versions

If your Opera service does not provide settlement codes, that field remains free text. The other available lists can still use dropdowns.

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. This setting does not control staff reservation notes.

Capability-based availability

The mapping section may keep Opera-specific wording. Its visibility follows the payment-mapping capability from your active PMS integration.

Configure Mews payment method mappings

Use Mews mappings when captured methods must appear under a specific enabled Mews payment category. Unconfigured methods keep their normal AVA posting behavior.

1. Confirm Mews is your active PMS in Settings → Essentials → PMS Integration.

2. Go to Settings → Payment.

3. Find Mews Payment Method Mappings.

4. Select a source payment method from the current payment catalogue. Sources can include PromptPay, card brands, wallets, or custom source codes.

5. Select an enabled Mews external payment category as the target.

6. Add another row only for a different source method.

7. Click Save.

   ✓ AVA validates each normalized source once before saving. ✓ Future Vouch postings use the selected Mews category.

Check the Mews category first

The target category must be enabled for your property in Mews. Ask your Mews administrator to enable it before saving the override. Existing payment records are not changed by a new mapping.

Clear an override

Remove a source row and save to restore that method's default posting behavior. This affects future Vouch postings only. Review existing records separately in Mews or your accounting report.

Configure Furama payment method mappings

Use Furama mappings when captured payments must use an active Furama iPMS payment type. The mapping card appears for a connected Furama property that supports payment overrides.

1. Confirm Furama iPMS is active in Settings → Essentials → PMS Integration.

2. Go to Settings → Payment.

3. Find Payment method mappings.

4. Select a Furama payment type under Record as for each payment method. Card methods map by brand, such as Visa or Amex. Named non-card methods map by method, such as Cash.

5. Click Save Payment Gateway Settings.

6. If needed, set Default payment type code (optional) in the Furama PMS settings.

7. Click Save PMS Settings.

   ✓ Explicit mappings are used first. ✓ The default code handles payment methods without an explicit mapping. ✓ Without either setting, AVA refuses the unmapped payment before posting it.

Verify the Furama code

Furama's catalogue is shared across a control unit and can include other hotels' codes. Choose an active code confirmed by your Furama administrator.

Clear a Furama mapping

Choose Use default and save to remove an override for that payment method. This affects future postings only.

Step 6: Configure Checkout Rounding Adjustment

AVA shows this control under Payment Policy Controls when your PMS supports it.

PMS provider	Support	Additional setup
AVA	Supported	No vendor code required
Opera / OHIP	Supported	Save the vendor code in Transaction Code (Rounding)
Cloudbeds, Mews, eZee, and Furama	Not supported	The control stays hidden

1. Go to Settings → Check-In → Check-In Policy.

2. Turn on Check-in outstanding-balance blocking or Checkout balance settlement.

3. Go to Settings → Payment.

4. Find Payment Policy Controls.

5. Turn on Enable Rounding Adjustment.

6. Set Rounding Threshold in your property's default currency.

7. If you use Opera, enter the vendor code in Transaction Code (Rounding).

8. Click Save Payment Policies.

   ✓ AVA applies the adjustment during checkout when the balance is within your threshold.

How the adjustment works

During check-in, AVA accepts a balance within the configured threshold without posting a transaction. During checkout, AVA posts the rounding adjustment before completing checkout. AVA uses no vendor code. Opera uses the configured vendor code.

Step 7: Configure Auto Delay Capture

Use Auto Delay Capture when your PMS supports delayed capture. AVA captures the room rate before the Stripe pre-authorization expires. The deposit remains uncaptured.

Setting	What it does
Enable Auto Delay Capture	Automatically captures the room rate before pre-authorization expiry
Auto Delay Capture Expiry Days	Sets how many days before expiry AVA captures the room rate

1. Go to Settings → Payment.

2. Find Payment Policy Controls → Pre-Authorization Controls.

3. Turn on Enable Auto Delay Capture.

4. Enter Auto Delay Capture Expiry Days.

5. Click Save Payment Policies.

   ✓ AVA captures the room rate before expiry when the pre-authorization remains valid.

Capability-based visibility

AVA shows these controls only when your active PMS reports delayed capture support. Opera currently reports support. Other PMS providers show the controls only after they report the same capability.

PMS changes can clear this setting

If you switch to a PMS without delayed capture support, AVA turns off Auto Delay Capture. AVA also clears its expiry-day value to prevent stale settings from being used.

Step 8: Configure Opera-Specific Payment Controls (Opera Only)

1. Go to Settings → Payment.

2. Find Opera-Specific Payment Controls.

3. Set payment behavior:

   • In-house invoice access and birthdate verification for check-out
   • Ignore Waive Payment Routing behavior

4. In Do Not Collect Any Incidental / Deposit, add each matching rate code, market segment, guarantee type, or comment.

5. Click Save Payment Policies.

   ✓ Matching incidental or deposit rows are removed from the payable balance.

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. Accommodation charge policies are configured above.

Rounding Adjustment Dependencies

Use this when you want checkout rounding to affect payment behavior.

1. Go to Settings → Check-In → Check-In Policy.

2. Turn on Check-in outstanding-balance blocking or Checkout balance settlement.

3. Return to Settings → Payment.

4. Open Payment Policy Controls and set Enable Rounding Adjustment.

   ✓ AVA applies the rounding setting only when one of those policies is on.

Saved value stays put

If you turn both check-in balance policies off later, AVA keeps the saved rounding value. The control only stops affecting payment behavior.

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
• ✅ A pre-authorization hold saves only with a deposit amount greater than 0
• ✅ Deposit currency stays saved after you click Save
• ✅ Auto Delay Capture appears only when your active PMS supports it
• ✅ PMS payment mapping appears when your active PMS reports support
• ✅ Opera policy sections appear only for Opera PMS
• ✅ The payment mapping card can appear for a non-Opera PMS when its integration reports support
• ✅ 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

Payment values fail validation

What you see: AVA marks a payment field invalid, or MCP returns valid: false.

Fix:

1. Use three uppercase letters for Deposit Currency.

2. Enter 0 or a higher value for Rounding Threshold.

3. Enter a whole number of 0 or higher for rounding codes and expiry days.

4. Correct the field, then click Save.

5. For MCP, run settings_validate again before applying the update.

   ✓ The validation result should show valid: true before you save or apply changes.

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.

Manual Stripe gateway save is rejected

What you see: AVA rejects a manual Stripe gateway save.

Fix:

1. Open Settings → Payment → Payment Gateway Integration.

2. Set Environment to Test.

3. Provide all three fields: Publishable Key, Secret Key, and Webhook Secret.

4. Leave masked values unchanged when re-saving existing credentials.

5. Save the payment gateway settings again.

   ✓ AVA saves the complete test configuration. ✓ A rejected save does not replace your existing credentials.

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.

Payment policy controls do not appear

What you see: Accommodation, checkout rounding, delayed capture, or Opera-specific payment controls are missing.

Fix:

1. Open Settings → Essentials → PMS Integration.
2. Confirm the active PMS is correct.
3. Return to Settings → Payment.
4. Refresh the page once.
5. Ask an administrator to confirm the PMS capability is enabled.

PMS payment mapping

Payment mapping appears when your active PMS reports support. Opera and Furama currently report this capability. The mapping section is separate from the other capability-gated payment policy controls.

Auto Delay Capture is missing

What you see: Pre-Authorization Controls does not show Auto Delay Capture.

Fix:

1. Open Settings → Essentials → PMS Integration.
2. Confirm the correct PMS is active.
3. Refresh Settings → Payment after changing PMS connections.
4. Ask your administrator or Vouch support whether the PMS reports delayed capture support.

If the PMS does not report support, the controls stay hidden. This is expected behavior.

Auto Delay Capture settings are rejected

What you see: AVA says delayed capture is unavailable when you save payment settings.

Fix:

1. Confirm the active PMS supports delayed capture.
2. Turn off Auto Delay Capture if you changed PMS providers.
3. Save the payment settings.
4. Retry after the PMS capability becomes available.

AVA does not save delayed capture settings for an unsupported or unverified PMS.

PMS 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 the correct PMS is active and reports payment mapping support.
3. Return to Settings → Payment.
4. Re-enter Default Cashier ID and each mapping row.
5. Click Save Opera Payment Mapping again.

Mews mapping options are unavailable

What you see: The Mews mapping card is missing, or source and target options do not load.

Fix:

1. Confirm Mews is the active PMS.
2. Refresh Settings → Payment after Mews finishes loading.
3. Confirm the payment catalogue and Mews configuration are available.
4. Contact support if the card remains unavailable.

AVA disables changes until it can validate the current source and target options.

Mews payment category is unavailable

What you see: AVA rejects a selected Mews payment category.

Fix:

1. Ask your Mews administrator to enable that category for the property.
2. Refresh Settings → Payment.
3. Select an enabled category from the refreshed list.
4. Save the mapping again.

Do not retry a payment until the mapping saves successfully.

Furama payment mapping options are unavailable

What you see: The Furama mapping card is missing, or its payment options do not load.

Fix:

1. Confirm Furama iPMS is the active PMS.
2. Confirm the Furama connection is saved.
3. Refresh Settings → Payment.
4. Check the Control Unit in Settings → Essentials → PMS Integration.
5. Ask your Furama administrator to confirm the payment catalogue is available.

AVA disables mapping changes until it can read the current source and target options.

Furama rejects a payment type

What you see: Furama rejects a payment after AVA starts posting it.

Fix:

1. Refresh Payment method mappings.
2. Replace the target with an active Furama payment type.
3. Confirm the code belongs to your property's control unit.
4. Set Default payment type code (optional) for unmapped methods, if needed.
5. Save both settings pages.
6. Retry the payment once.

Do not use a code marked inactive or a code from another property's catalogue.

Opera payment mapping is missing during payment

What you see: An Opera payment cannot start because its card-brand mapping is missing.

Why this happens: AVA may not have a current shared Opera configuration list.

Fix:

1. Wait for AVA to complete its automatic configuration refresh.

2. Retry the payment only if AVA still shows the error.

3. Check Opera PMS Payment Mapping in Settings → Payment.

4. Confirm the card brand has a matching payment method code.

5. Contact support if the mapping exists but the payment still cannot start.

   ✓ AVA makes this refresh once before sending an Opera payment request.

An Opera code list is empty

What you see: A cashier, settlement code, comment type, comment location, or payment method list is empty.

Fix:

1. Confirm the active PMS is Opera.
2. Check that the code exists and is active in Opera.
3. Refresh Settings → Payment.
4. Select another available code, if appropriate.
5. Contact your Opera administrator if the list remains empty.

AVA loads each list independently. Other mapping fields can still be configured.

Codes fail to load from OPERA

What you see: AVA shows "Could not load codes from OPERA."

Fix:

1. Confirm Opera is the active PMS.
2. Check that the Opera connection is configured and working.
3. Click Try again in Opera PMS Payment Mapping.
4. Enter codes manually when AVA keeps a field editable.
5. Contact support if the lists remain unavailable.

If a refresh fails, AVA keeps the codes read earlier and shows a refresh warning. If Opera returns a partial answer, AVA keeps successful lists and marks only the missing lists unavailable. Do not replace valid saved mappings unless Opera marks them unavailable.

Opera payment currency does not match

What you see: Opera shows an internal error, or a payment or deposit does not appear after posting.

Fix:

1. Check Property Currency in Settings → Essentials → Hotel Basic Details.
2. Make sure the Opera reservation uses the same currency.
3. Retry the payment or deposit.
4. Contact support if Opera still returns an internal error.

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 matching value if the reservation should not be waived.
4. Refresh AVA and test again with a new reservation.

Accommodation policy controls are unavailable

What you see: You do not see Accommodation Charge Policies, or AVA shows an unsupported PMS message.

Fix:

1. Confirm your PMS provider supports accommodation payment policies.
2. Refresh Settings → Payment.
3. If the controls still do not appear, AVA does not have support data for that PMS yet.
4. Keep existing policy values in place. AVA still stores them 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.

Mews included product needs review

What you see: A bundled Mews product needs review after a matching room-package waiver.

Why this happens: AVA could not prove the product's classification.

Fix:

1. Open the reservation through Staff Access.
2. Review the reservation rate, included products, and complete invoice in Mews.
3. Confirm the reservation matches the configured accommodation policy.
4. Refresh the reservation in AVA.
5. Do not collect an unverified amount.
6. Ask front-desk staff to review the complete Mews invoice.

Guest is sent to the front desk before payment

What you see: The guest cannot continue after reservation lookup. AVA asks the guest to see the front desk.

Why this happens: A payment policy matched, but Mews could not classify a governed charge.

Fix:

1. Review the Mews rate, included products, and complete invoice.
2. Confirm the matching value in Accommodation Charge Policies.
3. Refresh the reservation after Mews finishes syncing.
4. Confirm the payable amount with the complete Mews invoice.
5. Ask front-desk staff to complete the check-in when review remains necessary.

Do not collect an unverified amount.

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. For ACI, confirm Let assisted check-in staff collect payments is on at Settings → Check-In → Check-In Policy → Kiosk & payments.
4. Confirm the reservation has a balance due.
5. Save and retest with a new sample reservation.

ACI-only switch

The ACI switch does not change Self Check-In or Pre-arrival payment requests.

A zero deposit amount cannot be saved

What you see: AVA rejects the payment settings because the deposit amount is empty or 0.

Why this happens: A Pre-authorization hold needs a positive amount.

Fix:

1. Open Settings → Payment → Security Deposits & Incidentals.
2. Enter an amount greater than 0 in Deposit Amount.
3. Click Save Payment Gateway Settings.

If you do not want to collect a deposit, choose Do not collect. You can also click Switch to "Do not collect" instead in the inline error.

✓ AVA saves the safe collection choice and stops requesting a zero-value hold.

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.

Checkout rounding is unavailable

What you see: Enable Rounding Adjustment does not appear.

Fix:

1. Open Settings → Essentials → PMS Integration.
2. Confirm the active PMS provider.
3. AVA and Opera support checkout rounding.
4. Cloudbeds, Mews, eZee, and Furama do not currently support it.
5. Refresh Settings → Payment after a PMS connection change.
6. Contact support if AVA or Opera still hides the control.

Rounding adjustment stays inactive

What you see: Rounding adjustment stays gray, or the saved value does not change payment behavior.

Fix:

1. Open Settings → Check-In → Check-In Policy.
2. Turn on Check-in outstanding-balance blocking or Checkout balance settlement.
3. Save the settings.
4. Return to Settings → Payment and confirm the rounding value is still saved.

Still Stuck?

Contact success@vouch-technologies.com if:

• ❌ Payments still fail after re-saving settings
• ❌ Billing view changes do not appear for guests
• ❌ Delayed capture controls stay unavailable for a supported PMS
• ❌ Opera mapping values do not persist
• ❌ Mews mapping options or payment categories remain unavailable
• ❌ Stripe or Red Dot connection repeatedly disconnects

Helpful to include:

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

Related Guides

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