Adrasis™

Payments

Payments overview

Adrasis tracks money end to end: who pays whom, when, in which currency, and against which booking or contract. Four flows cover the lifecycle of a booking; each one stays connected to the rate plan and contract.

This page is the map. The four flows below each have their own dedicated page for the deeper reading.

Three currencies, one record. A traveller pays in their currency; the supplier contract is in another; your bank account settles in a third. Every conversion is recorded and reproducible, same inputs, same outputs.

The four flows

Traveller pays

pay-now · pay-deposit · pay-at-property

When a traveller books, money moves from the traveller to your organization. The rate plan defines which patterns are allowed; the booking flow captures the choice.

  • Pay-now in full, common for non-refundable rates and short lead times. Example: a 2-night Hotel Sunrise non-refundable booking for next weekend, EUR 360 charged at confirmation.
  • Pay-deposit-now, balance-later, typical for longer lead times. Example: 25% (EUR 180) on confirmation today, balance EUR 540 charged 7 days before check-in.
  • Pay-at-property, the traveller settles directly with the property; you do not collect their payment. Any separate supplier payout follows the agreed payment terms.

The traveller's payment follows the selected payment method. Console shows payment status without displaying full card numbers or security codes.

A card payment is charged by your own payment account, either now or as a hold on the card that you capture later. A guest who is not with you can pay from a payment link on your web shop. See Card payments and payment links.

You pay supplier

settlement · contract currency

Payment timing follows the supplier terms. Some bookings require immediate supplier payment; others are settled later, for example after the cancellation window closes. See Virtual cards for the supported card payment workflows. Settlement happens in the contract currency; the booking arrived in the traveller's payment currency; your organization settles in its bank-account currency. Three currencies, one transaction record.

The settlement surface batches transactions per contract per period, typically per night, per week, or per month, depending on the contract. The Console shows you what is due, in which currency, by when.

Example: Hotel Sunrise contract is monthly; on the 1st of each month you see one batch covering all bookings whose cancellation window closed in the previous month.

Cancellation refund

policy-driven · original payment method

When a traveller cancels within the refund window, money goes back. Adrasis reads the rate plan's cancellation policy, computes the refund amount (full, partial, none), and triggers the refund through the original payment method. The booking record carries the cancellation event and the refund chain.

Payment dispute

defense window · evidence flow

A payment dispute is a transaction reversal initiated by the cardholder through their bank, sometimes legitimately (fraud, mis-charged amount), sometimes opportunistically. The funds get pulled out of your account first, then you have a defense window (typically 7–14 days) to respond.

When that happens, Adrasis routes the case into a defense flow: gather the booking record, the cancellation policy, any operator notes, and submit them through the payment gateway. The decision lands back as evidence-accepted (you keep the funds) or evidence-rejected (the payment dispute stands).

Tax left for the guest to pay

A prepaid channel booking can still leave a tax for the guest to pay at the property. The same applies when the channel provides a virtual card and that card's amount leaves the tax out.

In the booking's payments panel, Tax paid at the property identifies this separate amount, owed by the guest at check-in. The channel's own amount stays separate. For example, if the channel sends 2000 TRY and the property's tax settings add 18.18 TRY, the booking total is 2018.18 TRY and the guest owes the 18.18 TRY tax at the property.

This row records an amount due. It does not mean the guest has paid it. Review its payment status before recording a receipt. If the channel price already contains the tax, select the matching treatment in the property's tax settings so it is not charged twice.

How payments tie to bookings

Contract → rate plan → booking → 4 payment record types
Every payment record carries a reference back to the booking, the rate plan, and the contract. When finance asks about a single transaction, the chain back to the contract is one click.

Currency conversion in practice

Three concrete scenarios on the Hotel Sunrise booking shape:

  • All-in-one currency. A German traveller pays EUR 720, the Hotel Sunrise contract is in EUR, your settlement bank account is in EUR. No conversions; no extra currency review needed.
  • Two-step conversion. A Turkish traveller pays TRY 24,000, contract is in EUR (Hotel Sunrise charges EUR 600 net), settlement is in TRY (your bank account). Adrasis records the TRY→EUR rate at booking time (for the contract liability) and the EUR→TRY rate at settlement (for the bank transfer).
  • Three-step conversion. A US traveller pays USD 800, contract is in EUR (Hotel Sunrise net EUR 600), settlement is in TRY. Each conversion is recorded separately.

Every conversion keeps the booking, contract, rate, and payout context together so finance can review a settlement without a separate spreadsheet.

Payment methods supported

Method Used for
Card (debit, credit) Primary traveller-side method, charged by your bank's virtual POS or your payment company account, in one payment or in installments where the account allows them.
Virtual card (linked to one payout and booking, with a fixed currency, limit, and automatic closure date) Organization → supplier payment in a supported currency.
Bank transfer High-value bookings, business-to-business settlements, batch supplier payments.
Alternative payment methods Wallets, regional payment schemes, surfaced where the traveller's market expects them.
Pay-at-property Traveller pays the property directly; Adrasis records the agreement.

Which methods are enabled per organization depends on your payment-gateway agreements and the markets you operate in. Adding a new method is an organization-configuration task.

AI Operator and payments

Use Adrasis AI Operator to review payment records. For example:

  • "Show me every booking with a balance due in the next 7 days."
  • "Show today's supplier payments for the Europe contracts."
  • "Find every cancellation in the last week where the refund hasn't processed."
  • "List the payment disputes we have open for more than 14 days."
  • "Show the virtual card status for Hotel Sunrise booking BK-12345."
  • "Capture 480 EUR of the hold on booking BK-12345."
  • "Send the guest of booking BK-12345 a payment link."

A refund, a hold capture or release and a payment link are prepared as a preview and run only after you approve them. The AI Operator does not take a new card payment and does not issue, close or change virtual cards. See Card payments and payment links and, for supplier payments, Virtual cards.

Where to next