arrow_backPerno Eduwallet
Payment reminders

Follow up on unpaid fees without starting from a blank email.

Create reusable reminder policies for the institution, attach them to fees and keep a visible history for every learner's charge.

schedule_send
What you get

Consistent, timely follow-up with less manual work.

schoolPerno Eduwallet
account_treePerno Orchestration
verified_userPayment reminders
Verified platform activity

Built on payment infrastructure already working in production.

A conservative snapshot of Perno's production footprint—not a forecast or an invented customer claim.

price_check
55k+

successful production payments recorded

account_balance
3

payment providers represented in live transactions

domain
5

specialist industry payment products

account_tree
976k+ PLN

processed payment value in the leading production currency

Live database snapshot for 30 October 2026. Values are rounded down and sandbox transactions are excluded. Different currencies are not combined.

Inspect the product evidence: See what we ship View supported PSPs Explore the API
Why change

Payment follow-up should be a policy, not a daily memory test.

These are operational problems, not just payment-screen problems.

check_circle

Staff manually decide who to contact each day.

check_circle

Messages are inconsistent and their history is difficult to audit.

check_circle

Optional fees continue creating noise after their due date.

What you get

Configure the follow-up once, retain control every time.

date_range

Before and after due date

Schedule messages relative to the due date instead of managing calendar reminders.

translate

Institution language

Communicate with payers in the language configured for the institution.

link

Direct payment action

Bring the payer back to the relevant payment request and current amount due.

history

Reminder history

See what was sent and when on the charge detail page.

pause_circle

Pause per charge

Stop follow-up for one specific situation without disabling the institution policy.

rule

Optional-fee logic

Avoid inappropriate overdue follow-up where an optional charge should simply lapse.

How it works

Consistent, timely follow-up with less manual work.

Step 01

Create a policy

Define the timing and message for each reminder step.

Step 02

Assign it to fees

Choose the default or a specific policy when creating the charge or plan.

Step 03

Review exceptions

Use history and pause controls for cases that need personal handling.

Common uses

A useful cadence, not message overload.

check_circleAdvance due-date notice
check_circleReminder on the due date
check_circleFirst overdue follow-up
check_circleSecond overdue escalation
check_circleA different policy for optional fees
check_circleA paused case under discussion
Questions

Payment reminders

Can we use different reminder policies?add

Yes. One reminder policy can be assigned to many charges, and different fees can use different policies.

Can staff stop reminders for one payer?add

Yes. Reminder sending can be paused for the specific charge without changing other learners' schedules.

Turn polite, consistent follow-up into part of the process.