AsentTime supports taking a deposit or full payment as the booking is made. Payments run through iyzico or PayTR with 3D Secure verification, and card details are never stored in the system. Your takings are visible in the panel and feed the revenue reports.
When no payment is taken, a customer's commitment is verbal only. That pushes no-show rates up sharply, particularly for long and higher-value services.
Every transaction is verified by the cardholder's bank. Card data is processed at the payment provider and never stored here.
You decide which services require prepayment and how much — a fixed amount or a percentage of the service price.
Choose iyzico or PayTR, whichever suits you. Your provider credentials are stored encrypted.
Payments received are reported by service, staff member and date, with revenue trends shown as charts.
A scheduled background job compares transaction states at the provider with records in the system and corrects any discrepancies.
A sub-merchant structure is supported, letting takings be transferred directly to your business.
How binding a booking feels is proportional to what the customer has invested in it. When nothing has been paid, the cost of not turning up is zero.
Even a small deposit changes that balance. A customer who has paid either attends or cancels in advance — and the second is valuable to you too, because the slot can be resold.
You can set the deposit per service. Not asking for prepayment on short, low-value services while requiring it on long, high-value ones is a common and sensible approach.
Card details are never written to the AsentTime database. The customer enters them on the provider's secure page, and only the outcome of the transaction returns to the system.
Your provider account credentials — the API keys — are stored encrypted. Even someone with direct database access could not read them in usable form.
Every transaction passes through 3D Secure and is not completed until the customer's bank approves it, which protects both the business and the customer.
The most common problem in online payments is a transaction that succeeded at the provider but was never completed in the system — usually because of a network interruption or a browser closed too early.
AsentTime solves this with reconciliation: a job running on a schedule compares transaction states at the provider with the records here and corrects the differences.
Nothing the customer paid for is left invisible in the system, which matters for both accounting accuracy and customer trust.
Set up your iyzico or PayTR account from the panel.
Decide which services require prepayment and how the amount is calculated.
Make a booking yourself and verify the payment flow end to end.
Track payments and revenue trends from your panel.
iyzico and PayTR. You pick whichever suits you and enter the account details in the panel.
No. Card data is processed on the provider's secure infrastructure and only the transaction result is returned.
Yes. You decide per service whether prepayment is required and how much it should be.
A scheduled reconciliation job compares the provider's records with the system and corrects the discrepancy.
That depends on the account structure you have with your provider. With a marketplace (sub-merchant) setup, payments are transferred to your business.
Setup takes minutes and no card is required. You can use every feature free of charge during the trial period.