# 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. {% hint style="info" %} **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. {% endhint %} *** ## 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 move their money. Usually combined with a virtual card on your side. The traveller's payment method (card, bank transfer, regional payment scheme) flows through a certified payment gateway — Adrasis never sees raw card numbers. *** ### You pay supplier *** `settlement · contract currency` After a booking lands and (for refundable rates) the cancellation window closes, you settle with the supplier. 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. *** ### Chargeback *** `defense window · evidence flow` A chargeback 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 chargeback stands). *** ## 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. | | **Virtual card** *(single-use payment instrument issued per booking, in the supplier's currency, with a fixed limit)* | Organization → supplier settlement, especially across currencies. | | **Bank transfer** | High-value bookings, B2B 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 a organization-configuration task. *** ## Adragent and payments Common phrases that map to Adragent payment operations: * *"Show me every booking with a balance due in the next 7 days."* * *"Run today's supplier settlements for the Europe contracts."* * *"Find every cancellation in the last week where the refund hasn't processed."* * *"List the chargebacks we have open for more than 14 days."* * *"Issue a virtual card for the Hotel Sunrise booking BK-12345 in EUR."* Read operations return immediately; writes preview before applying. See [Confirm-before-apply](/console/adragent/confirm-before-apply.md). *** ## Where to next * **Virtual cards in detail** → [Virtual cards](/console/payments/virtual-cards.md) * **Settlement and reconciliation** → [Settlement & reconciliation](/console/payments/settlement-and-reconciliation.md) * **Refunds and chargebacks** → [Refunds & chargebacks](/console/payments/refunds-chargebacks.md) * **The contracts that drive payment terms** → [Contracts](/console/contracts-and-onboarding/contracts.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://adrasis.gitbook.io/console/payments/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.