Module · Payments
Money settings
Where: ExpertPress → Money → Settings (Гроші → Налаштування)
Who can open it: staff with expertpress_manage_money (administrators, managers and accountants). Who can change each option is marked on the option:
- Administrator only — technical settings. Managers and accountants see them read-only, with the note "Mode, bank, cash register, money scheme, and cashier logins are technical settings. An administrator changes them; here they are read-only."
- Administrator or manager — money policy (platform fee, refund hours, complaint deadlines). An accountant sees them read-only. Every change to these is logged and listed as a payment rule under Settings → History of settings changes (see Settings history).
- Anyone with money access — wording and accounting fields.
What this tab is for
This tab sets how clients pay, which providers are used, how much the platform keeps, how refunds and payouts work, and what appears on receipts. It has one form, saved with Save, and three panels:
- Constants (administrators only): which secret constants from
wp-config.phpare set. See Payment providers. - Payout route: shown when Stripe is involved. See Stripe payouts.
- Manual refund: refund a booking by its number. See Manual refund.
Administrators also see an Online payments button that opens the activation page.
How saving works
- A field the form did not send keeps its value; saving never resets what was not on the screen.
- When part of a save is refused (for example live mode without a live cash register), the screen says why and adds "Other settings saved." The rest of the form is stored.
- If someone else saves at the same moment: "Settings were not saved: another change is being saved right now. Try again."
- On success: "Money settings saved. Secrets stay in wp-config.php."
- A payment that is already open keeps the terms it was created with (money scheme, refund threshold, platform fee, receipt issuer). New values apply to new payments.
Some values are shared with the core plugin: Shop currency is the same value as Settings → General → Pricing currency, and the complaint deadlines and the two session-completion windows are the values the core uses for bookings and complaints.
The options below are listed in the order they appear on the screen.
Mode and currency
Mode
- Where: ExpertPress → Money → Settings, first row (Режим). Administrator only.
- What it does: Test (Тест) uses the test providers and moves no real money. Live (Реальні платежі) allows real charges.
- Default: Test.
- Values / limits: Test, Live. Live needs real provider credentials. It is saved only when every enabled payment method allows live mode (only monobank in this version), the cash register is not the test one, and its live credentials are set. Otherwise the save keeps Test and lists the reasons under "Live mode will not be saved:". Saving Live with the virtual bank as payout method switches payouts to the manual method.
- When to change it: when you launch with real money after testing the whole flow; back to Test to try a new provider setup without real charges.
- Related: Going live
Shop currency
- Where: same form (Валюта магазину). Administrator only.
- What it does: The currency of service prices, payments, refunds and payouts. It is the same value as the core Pricing currency.
- Default: chosen once from the site language on first activation (see Pricing currency).
- Values / limits: any ISO 4217 currency from the list. A change is refused while any payment, refund or payout has been recorded, while money is still in progress, or while published services are priced in another currency; recorded amounts are never converted. Payment methods that do not accept the new currency are turned off ("… was not turned on: it does not accept …"); monobank accepts UAH only. With Stripe payouts on, the new currency must be a Stripe settlement currency, otherwise "The shop currency was not changed: … The previous currency stays."
- When to change it: only before the first payment, for example UAH for a monobank site or EUR for a Stripe test site.
- Related: Payment providers
Payment methods
There is one pair of rows for each provider: Test bank, Monobank and Stripe (test mode). Each Payment method row's hint shows "Ready." or "Not ready:
Payment method:
- Where: same form, below Shop currency (Спосіб оплати: …). Administrator only.
- What it does: On offers this provider to clients on the booking page. With more than one method on, the client picks one under Payment method before paying.
- Default: Test bank On; Monobank and Stripe Off.
- Values / limits: Off, On. At least one method must stay on ("Payment methods were not changed: at least one must be on."). A method that does not accept the shop currency is not turned on. The bank split works only with a single method on. A provider turned on without its keys is saved, but its row says "Not ready: no keys for the current mode." and clients cannot pay with it. Monobank and Stripe need real provider credentials.
- When to change it: turn monobank on and the test bank off before going live in UAH; turn Stripe on next to the test bank to try card holds and Stripe payouts.
- Related: Payment providers
Order on the payment page:
- Where: same form, under each Payment method row (Порядок на сторінці оплати: …). Administrator only.
- What it does: The position of this method in the client's list; "1 is shown first." The first method is also used for money created without a client's choice.
- Default: 1 for the test bank; empty for methods that are off.
- Values / limits: a whole number. Empty or non-numeric puts the method last; equal numbers keep the order Test bank, Monobank, Stripe.
- When to change it: put the provider most of your clients use first; put a new provider last while you watch how it works.
- Related: Payments in the booking flow
Locale and payout details
Settlement timezone
- Where: same form (Часовий пояс розрахунків). Administrator only.
- What it does: "Used for payout cutoffs, business days, and the transfer calendar day." It decides when the weekly accrual cutoff happens, which days count as business days for payout deadlines, and the date of a transfer.
- Default: empty, meaning the WordPress timezone (shown as "WordPress timezone (…)").
- Values / limits: a timezone from the list. An invalid value is refused ("The settlement timezone was not changed: the value is not a valid timezone."). A site plugin may override it.
- When to change it: your accountant and bank work in another zone than the site. Keep it equal to the platform time zone if payout months should match monthly statements; the Reports tab warns when they differ.
- Related: The weekly payout cycle
Specialist payout details pack
- Where: same form (Пакет реквізитів спеціаліста). Administrator only.
- What it does: "Field rules for specialist IBAN and tax id." Decides what specialists enter as payout details.
- Default: International (any IBAN country).
- Values / limits: International (any IBAN country) (Міжнародний (будь-яка країна IBAN)); Ukraine (IBAN UA, EDRPOU / IPN) (Україна (IBAN UA, ЄДРПОУ / ІПН)) — Ukrainian IBAN only, an 8-digit EDRPOU or 10-digit IPN, tax number always required. A site plugin may override the country.
- When to change it: choose Ukraine when all specialists are paid to Ukrainian accounts; keep International for a mixed-country marketplace.
- Related: Payout details
Ways specialists can receive payouts
- Where: same form, checkboxes (Способи отримання виплат спеціалістами). Administrator only.
- What it does: Which kinds of account specialists may choose on their Finances page.
- Default: IBAN, US bank account (ACH), UK bank account (sort code), International transfer (SWIFT/BIC).
- Values / limits: IBAN; US bank account (ACH); UK bank account (sort code); International transfer (SWIFT/BIC); Payment provider account. Applies to the International pack only (the Ukraine pack allows IBAN). Unticking everything leaves IBAN. Account numbers other than IBAN are stored encrypted and need
EXPERTPRESS_FISCAL_STORAGE_KEYinwp-config.php. - When to change it: leave only IBAN for a European marketplace; add US ACH when you onboard US specialists.
- Related: Payout details
Tax number is required
- Where: same form, checkbox (Податковий номер обов’язковий). Administrator only.
- What it does: Makes the tax number a required part of the specialist's payout details.
- Default: off (always required in the Ukraine pack).
- Values / limits: on / off.
- When to change it: your accountant needs a tax number for every payout.
- Related: Payout details
Keep payout details (years)
- Where: same form (Зберігати реквізити виплат (років)). Administrator only.
- What it does: "After this period the bank details in finished payouts and replaced payout details are erased; amounts, dates and statuses stay." A daily background task does the clean-up.
- Default: 5 years.
- Values / limits: 1 to 30; values outside are brought into range.
- When to change it: match the period your accountant must keep payment records.
- Related: Data retention
Payment and payout texts
Payout purpose template
- Where: same form (Шаблон призначення платежу). Anyone with money access.
- What it does: The purpose text of a payout transfer. Placeholders:
{id}and{payout_id}(both the payout number). A site plugin may override the final text. - Default:
Payout {id}. - Values / limits: plain text, up to 160 bytes; empty restores the default.
- When to change it: "Payout {id} under the service agreement"; a text in your bank's language.
- Related: Paying out
Booking payment line (client)
- Where: same form (Рядок оплати запису (клієнт)). Anyone with money access.
- What it does: The name of a booking payment that the client sees at the bank and on the receipt. Placeholders:
{service},{specialist},{booking},{site}. If{service}is empty it falls back to "Booking N". A site plugin may override the final text. - Default:
{service}. - Values / limits: up to 200 bytes (the monobank limit); longer text is cut. Empty restores the default.
- When to change it: "{service} with {specialist}"; "{site}: booking {booking}" so clients recognise the charge on their statement.
- Related: monobank
Booking payment line (specialist share)
- Where: same form (Рядок оплати запису (частка спеціаліста)). Anyone with money access.
- What it does: The basket line for the specialist's share on a bank-split invoice. Same placeholders; an empty
{service}falls back to "Service". - Default:
{service}. - Values / limits: up to 200 bytes; empty restores the default. Used only with the bank split.
- When to change it: "{specialist}: {service}" so the split lines are easy to tell apart in the bank statement.
- Related: Money scheme
Promotion / platform sale payment line
- Where: same form (Рядок оплати просування / продажу платформи). Anyone with money access.
- What it does: The name of a payment for a product the platform itself sells to specialists (for example paid promotion from another ExpertPress module). Placeholders:
{service},{site},{sale}. - Default:
{service}(the product title). - Values / limits: up to 200 bytes; empty restores the default.
- When to change it: "{site} promotion #{sale}" so specialists recognise the charge.
- Related: Paying for purchases from the specialist's balance
Providers and money scheme
Monobank saved-card wallet
- Where: same form (Гаманець збережених карток Monobank). Administrator only.
- What it does: "Allows save-card / token charges when Monobank is the payment provider." In this version card saving through monobank is not connected: even with the switch on, payments that need a saved card are refused with "Monobank card saving is not configured."
- Default: Off.
- Values / limits: Off, On. Not a secret; monobank tokens stay in
wp-config.php. - When to change it: leave it off in this version.
- Related: monobank
Checkbox fiscal service
- Where: same form (Фіскальний сервіс Checkbox). Administrator only.
- What it does: Makes Checkbox available under Cash register.
- Default: Off.
- Values / limits: Off, On. Needs real provider credentials (the Checkbox constants).
- When to change it: you have a Checkbox account and need fiscal receipts, at the latest before going live.
- Related: Checkbox
Cash register
- Where: same form (Каса). Administrator only.
- What it does: Which service issues payment and refund receipts.
- Default: Test cash register.
- Values / limits: Test cash register (Тестова каса); Checkbox (only when Checkbox fiscal service is On; otherwise the save falls back to the test register). The test register is refused in live mode.
- When to change it: choose Checkbox before going live; keep the test register while you set up the site.
- Related: Checkbox
Money scheme
- Where: same form (Схема розрахунків). Administrator only.
- What it does: Who receives the client's money. Through the platform's account (Через рахунок оператора): the whole payment goes to the platform and the specialist's share is paid out later. Bank split (Розподіл платежу банком): the bank splits each payment between the specialist and the platform at the moment of payment.
- Default: Through the platform's account.
- Values / limits: The bank split is saved only when exactly one payment method is on and that provider supports it (the test bank; monobank in test mode). Otherwise "The split scheme was not saved: …". The split also sets Who issues the receipt to the specialist. With the split, each specialist needs a receiver id with the bank, and a special rate of 100% is refused because it leaves no share.
- When to change it: your bank and your agreements with specialists require money to reach specialists directly; keep the default when the platform pays specialists itself.
- Related: Who issues the receipt
Fee, refunds and session completion
Platform fee (%)
- Where: same form (Комісія платформи (%)). Administrator or manager.
- What it does: The share of each booking payment the platform keeps; the rest is the specialist's share. A special rate on the Rates tab replaces it for one specialist. Each booking keeps the fee that applied when it was created.
- Default: 20%.
- Values / limits: 0 to 100, with at most two decimals (for example 20 or 12.5). An invalid value is refused: "Platform fee was not changed: enter a percent from 0 to 100 with at most two decimals, for example 12.5."
- When to change it: a lower fee during launch to attract specialists; a higher fee if the platform also handles marketing and support.
- Related: Rates
How many hours the client has to confirm the session took place or report a problem
- Where: same form (Скільки годин має клієнт, щоб підтвердити, що консультація відбулася або повідомити про проблему). Administrator only.
- What it does: After the specialist marks the session as held, the client has this long to confirm or report a problem. "After this period, the session is considered completed, the conversation closes, and the amount becomes available for payout under the payout rules."
- Default: 24 hours.
- Values / limits: whole hours, 1–168. An empty, fractional or out-of-range value resets the field to 24. Each booking keeps the value it was created with.
- When to change it: 48 hours if clients often miss the confirmation request; 12 hours for faster payouts on short sessions.
- Related: Completing the session
How many hours the specialist has after the session ends to mark it as completed
- Where: same form (Скільки годин має спеціаліст після закінчення консультації, щоб позначити її проведеною). Administrator only.
- What it does: "If the specialist does not mark the session as completed in time, the booking goes to manual review."
- Default: 48 hours.
- Values / limits: whole hours, 1–168. An empty, fractional or out-of-range value resets the field to 48. Each booking keeps the value it was created with.
- When to change it: shorter (24 h) if specialists are used to marking sessions right away; longer (72 h) for weekend-heavy schedules.
- Related: Completing the session
Full refund if at least this many hours remain before the start
- Where: same form (Повне повернення, якщо до початку залишається щонайменше вказана кількість годин). Administrator or manager.
- What it does: The refund threshold. When the client cancels at least this many hours before the start, they get a full refund; later, no refund. When the specialist cancels at least this many hours before, the client gets a full refund at once; later, the client chooses (see the next option). The threshold is fixed on each booking's payment and shown to the client before and after paying.
- Default: 24 hours.
- Values / limits: 1–168; values outside are brought into range.
- When to change it: 48 hours for sessions that need preparation; 12 hours for short consultations often booked the same day.
- Related: Refund rules
Late cancellation by the specialist: hours for the client to choose before the automatic refund
- Where: same form (Пізнє скасування спеціалістом: годин клієнту на вибір до автоповернення). Administrator or manager.
- What it does: "The client can move the payment to another time or request a refund; if they do not respond, the full amount is refunded automatically after this period."
- Default: 48 hours.
- Values / limits: 1–336 (two weeks); values outside are brought into range.
- When to change it: 24 hours if clients expect quick refunds; longer if most clients prefer to rebook with the same specialist.
- Related: Refund rules
Payouts and debts
Specialist payout method
- Where: same form (Спосіб виплат спеціалістам). Administrator only.
- What it does: How the specialist's share is sent.
- Default: Virtual bank (test).
- Values / limits: Virtual bank (test) (test mode only); Manual: bank transfer and payment order number; Stripe transfer (test mode) — disabled in the list until the Stripe payout route is ready, and refused unless Stripe is on as a payment method. In live mode the virtual bank is replaced by the manual method. Stripe needs real provider credentials.
- When to change it: choose Manual before going live; choose Stripe to test Stripe Connect payouts.
- Related: Stripe payouts, Paying out
Accrual day (cutoff at 00:00 )
- Where: same form (День нарахування (відсічка о 00:00 …)). Anyone with money access.
- What it does: The weekday on which the weekly payout calculation closes, at midnight in the settlement timezone. Earnings that became payable before the cutoff are included in that week's payout.
- Default: Monday.
- Values / limits: Monday … Sunday.
- When to change it: align it with your accountant's routine, for example Thursday for transfers on Friday.
- Related: The weekly payout cycle
The agreement allows offsetting the specialist's debt against future payouts
- Where: same form (Договір дозволяє погашати борг спеціаліста за рахунок майбутніх виплат). Administrator only.
- What it does: Yes: a specialist's debt is taken off their next payouts, oldest debt first (booking debt from booking earnings, shop debt from shop earnings), and staff can issue repayment requests. No: no set-off; a payout to a specialist with a debt needs a written decision reason.
- Default: No.
- Values / limits: No, Yes. The setting records what your agreement allows; the module does not check the agreement.
- When to change it: your specialist agreement contains a set-off clause.
- Related: Debts
Paying for purchases from the specialist's balance (balance offset clause)
- Where: same form (Оплата покупок з балансу спеціаліста (умова договору про зарахування коштів)). Administrator only.
- What it does: Yes lets a specialist pay for a platform product (for example paid promotion) from their available balance instead of a card.
- Default: No.
- Values / limits: No, Yes. Has an effect only with a module that sells products to specialists.
- When to change it: your agreement allows it and specialists ask to pay for promotion from their earnings.
- Related: Promotion / platform sale payment line
Request to repay the debt — after this many days without new accruals
- Where: same form (Вимога повернути борг — після вказаної кількості днів без нових нарахувань). Anyone with money access.
- What it does: How long a specialist with a debt must go without new earnings before staff can issue a repayment request (Issue a repayment request on the Payouts tab). Requests are possible only when the set-off clause above is Yes.
- Default: 30 days.
- Values / limits: 1–365.
- When to change it: shorter (14 days) if debts should be settled quickly; longer for specialists who work seasonally.
- Related: Debts
Complaints
These deadlines and the team email are shared with the core complaint process. See Complaints.
Decision on a complaint — within this many business days
- Where: same form (Строк рішення за скаргою (робочі дні)). Administrator or manager.
- What it does: The deadline for the team's decision on a complaint. The specialist's payout for the booking stays on hold while the complaint is open.
- Default: 10 business days.
- Values / limits: 1–30.
- When to change it: shorter (5 days) if you have a dedicated support person; longer during holidays.
- Related: Complaints
Deadline for a party's explanation in a case, hours
- Where: same form (Строк пояснення сторони у справі, годин). Administrator or manager.
- What it does: How long the client or specialist has to answer the team's request for an explanation.
- Default: 48 hours.
- Values / limits: 1–336.
- When to change it: 24 hours for fast decisions; 72 hours if participants are in many time zones.
- Related: Complaints
A specialist can complain about a client within this many days after the session
- Where: same form (Спеціаліст може поскаржитися на клієнта протягом вказаної кількості днів після консультації). Administrator or manager.
- What it does: How long after the session the specialist can use Complain about the client.
- Default: 7 days.
- Values / limits: 1–60.
- When to change it: longer (14 days) if problems such as chargebacks tend to appear later.
- Related: The booking flow — Complaints
Team email for complaints
- Where: same form (Пошта команди для скарг). Administrator or manager.
- What it does: Where complaint notifications for the team are sent. "Empty means the site administrator's email."
- Default: empty.
- Values / limits: one valid email address; an invalid address is saved as empty.
- When to change it: route complaints to a shared support inbox instead of the administrator.
- Related: Complaints
Receipt details
Who issues the receipt
- Where: same form (Хто пробиває чек). Administrator only.
- What it does: The platform, one cash register (Оператор, одна каса) issues every receipt from the platform's register. Specialist, own cash register (Спеціаліст, своя каса) issues each specialist's receipts from their own register.
- Default: The platform, one cash register.
- Values / limits: the two values above; forced to the specialist with the bank split. With specialists' registers, live payments need
EXPERTPRESS_FISCAL_STORAGE_KEYand each specialist's register set up. - When to change it: specialists are independent sellers who must issue their own receipts.
- Related: Checkbox
Platform sole proprietor (placeholder)
- Where: same form (ФОП оператора (заглушка)). Anyone with money access.
- What it does: The name printed on receipts from the platform's register as "Payment is accepted by … as an agent." When empty, Agent name in the receipt text (or the site name) is used.
- Default: empty.
- Values / limits: plain text, up to 160 bytes.
- When to change it: enter the legal name your accountant tells you to show on receipts.
- Related: Agent name in the receipt text
Platform tax ID (placeholder)
- Where: same form (РНОКПП оператора (заглушка)). Anyone with money access.
- What it does: A stored platform tax number. In this version it is not printed on receipts.
- Default: empty.
- Values / limits: digits only, up to 12.
- When to change it: no effect on receipts in this version; fill it only for your own records.
- Related: Platform sole proprietor (placeholder)
Platform IBAN (placeholder)
- Where: same form (IBAN оператора (заглушка)). Anyone with money access.
- What it does: A stored platform IBAN. In this version it is not printed on receipts.
- Default: empty.
- Values / limits: letters and digits, up to 34, stored in upper case.
- When to change it: no effect on receipts in this version; fill it only for your own records.
- Related: Platform sole proprietor (placeholder)
Specialist sole proprietor, one placeholder for all test specialists
- Where: same form (ФОП спеціаліста, одна заглушка на всіх тестових). Anyone with money access.
- What it does: One stored name for all specialists, meant for testing. In this version it is not printed on receipts.
- Default: empty.
- Values / limits: plain text, up to 160 bytes.
- When to change it: only while testing receipts.
- Related: Specialist's tax ID (placeholder)
Specialist's tax ID (placeholder)
- Where: same form (РНОКПП спеціаліста (заглушка)). Anyone with money access.
- What it does: When filled, added to the header of every session receipt as "Tax ID …". The same value is used for all specialists, so it is meant for testing. In test mode the receipt also says "Requisites are a placeholder."
- Default: empty.
- Values / limits: digits only, up to 12.
- When to change it: fill it while testing how receipts look; leave it empty on a live site with many specialists.
- Related: Test cash register
Specialist's IBAN (placeholder)
- Where: same form (IBAN спеціаліста (заглушка)). Anyone with money access.
- What it does: When filled, added to the header of every session receipt as "IBAN …", for all specialists.
- Default: empty.
- Values / limits: letters and digits, up to 34, stored in upper case.
- When to change it: as for the tax ID above: for testing only.
- Related: Test cash register
Platform cashier login (test)
- Where: same form (Логін касира оператора, тест). Administrator only.
- What it does: The Checkbox cashier login for the platform's register in test mode. The password and license key go into
wp-config.php. - Default: empty.
- Values / limits: plain text, up to 80 bytes. Needs real provider credentials.
- When to change it: when you connect a Checkbox test cash register.
- Related: Checkbox
Platform cashier login (live)
- Where: same form (Логін касира оператора, живий). Administrator only.
- What it does: The Checkbox cashier login for the platform's register in live mode.
- Default: empty.
- Values / limits: plain text, up to 80 bytes. Required to save live mode with the platform's Checkbox register ("There is no cashier login for live mode."). Needs real provider credentials.
- When to change it: before going live with the platform's register.
- Related: Going live
Product tax code in the platform's cash register
- Where: same form (Податковий код товару в касі оператора). Anyone with money access.
- What it does: The tax code sent with each receipt line from the platform's register. A specialist's own register uses the specialist's own code when one is set.
- Default: empty.
- Values / limits: digits only, up to 10.
- When to change it: enter the code your Checkbox cash register uses for the service; ask your accountant which one.
- Related: Checkbox
Agent name in the receipt text
- Where: same form (Назва агента в тексті чека). Anyone with money access.
- What it does: The agent name in the receipt text when Platform sole proprietor is empty. "Empty means the site name (“…”). A saved value does not change by itself."
- Default: empty (the site name).
- Values / limits: plain text, up to 160 bytes.
- When to change it: the site name is a marketing brand and receipts should show the company name instead.
- Related: Brand name
Manual refund
Where: ExpertPress → Money → Settings, Manual refund panel (Ручне повернення). Anyone with money access.
Fields: Booking ID, Amount,
- An empty amount refunds the whole remaining balance.
- A smaller amount is a partial refund, which only a person can start: "Automation never starts a partial refund."
- The panel suggests refunding from the booking card instead, which shows the payment, earlier refunds and the split. See Manual and partial refunds.
Settings without a field on this screen
The money engine stores a few more values that have no field on this tab:
- Shop commission and shop hold days (defaults: the platform fee, and 14 days): the fee and the waiting time for goods sold through a shop module.
- When a booking is charged (default: when the specialist accepts) and the timings for the alternative "hold before the session" and "charge after the session" modes. These modes need every enabled payment method to be able to hold money and save a card (the test bank or Stripe).
This screen offers no way to change them; they keep their defaults unless a site plugin or developer sets them.