# Online payment automations

What online payments do by themselves: the job that books confirmed payments, the three Moyasar jobs behind automatic card charges, and the three e-mails a client receives when such a charge fails, with how to stop each one.

Online payments run four scheduled jobs and send three e-mails. Only the first job concerns every invoice paid online; the rest serve automatic charges on saved cards, explained in [How an online payment reaches the books](how-an-online-payment-reaches-the-books), and do nothing while no such charge is active. An administrator starts or stops a job from the scheduled actions of the technical menu; a test or restored copy of the database starts with all of them stopped.

## Scheduled jobs {#jobs}

### Payment: Post-process transactions {#post-process}

- **When:** every ten minutes, while at least one provider is not **Disabled**. It switches itself on when a provider leaves **Disabled** and off when the last one is disabled.
- **What it does:** finishes the bookkeeping of the payments the client's return to the site did not finish: it creates the payment in the provider's **Payment Journal** and matches it with the invoice. It keeps trying for four days after the transaction last changed state.
- **How to stop it:** disable the providers; stopping the job alone leaves confirmed payments out of the books.

### Moyasar: Process Recurring Charges {#recurring}

- **When:** every hour.
- **What it does:** charges every active recurring charge whose next charge date has come, and every retry that is due.
- **How to stop it:** pause or cancel the recurring charge itself; deactivating the job stops all of them.

### Moyasar: Settle Charged Cycles {#settle}

- **When:** every hour.
- **What it does:** completes the bookkeeping of cycles paid but not yet recorded, asks Moyasar again about any charge left without an answer for more than an hour, and, after four days, gives the creator of the recurring charge a to-do **Charge collected but not reconciled**, never charging the client a second time.
- **How to stop it:** deactivate the job; nothing is charged by it.

### Moyasar: Refresh Saved Card Status {#refresh-cards}

- **When:** once a day.
- **What it does:** asks Moyasar for the status of every saved card that an active recurring charge uses. A card that is no longer usable gets a note on the recurring charge and the e-mail **Moyasar: Saved Card No Longer Valid**.
- **How to stop it:** deactivate the job.

## E-mails to the client {#emails}

The three e-mails go to the client of the recurring charge, in the client's language, from the company's address, and wait in the outgoing queue like any other e-mail. Each one is named on the dunning policy, under **Notifications**; empty a field to stop that e-mail. The default policy, **Standard (3 attempts over 1 week)**, tries a charge three times, a day then three days apart, and stops at once on a decline that cannot change by itself, such as an expired card.

![The default dunning policy, with its retries and the three e-mails it sends.](https://jaah.app/web/image/11376-804fb314/online-payments-automations-dunning_policy-en.png)

### Moyasar: Automatic Charge Failed {#charge-failed}

Subject **Your payment could not be processed**. Sent after a failed attempt when another one is scheduled; the date of the next attempt is noted on the recurring charge.

### Moyasar: Automatic Charging Stopped {#charging-stopped}

Subject **We could not process your payment**. Sent when the last attempt fails or the decline is final. The recurring charge moves to **Attempts Exhausted** and its creator gets a to-do **Automatic charging stopped**.

### Moyasar: Saved Card No Longer Valid {#card-unusable}

Subject **Your saved card needs to be updated**. Sent by the daily card check when the saved card can no longer be charged.

---

- Source: https://jaah.app/docs/online-payments/online-payments-automations
- Updated: 2026-10-23
- Version: Online payments 19.0.1.3.0
- Verified: 2026-10-23