Email Notifications
What U.CASH emails you and your customers, and how to configure delivery.
Merchant notifications
Under Settings → Email, toggle each notification type (all delivered to your notification email):
| Notification | When it fires |
|---|---|
| Payment received | Every completed payment - and rejected underpayments, with an [Underpayment] subject |
| Transfer completed | Auto-sweeps of settled crypto to your wallets (and failures) |
| Conversion completed | Exchange conversions to fiat (and failures) |
| Admin login | Each console login, with time and IP |
Operational emails you always receive: payout info submitted, low credit balance warnings, and a payment-blocked notice when your credit balance cannot cover new checkout fees.
Customer emails
- Payment confirmation - receipt with amounts, transaction id, and your business profile, sent in the customer's saved language
- Payment request - "You have received a payment request" with a Pay Now button and expiry notice
- Payout info request - "Provide Payout Info" link for payees (see Payouts)
- Purchase complete (shop) - customizable subject and body with merge fields like
{license_key},{invoice_url}, and{downloads_url}
Delivery setup
- Delivery runs on the platform's mail infrastructure by default - nothing to configure
- Self-hosted and white-label builds can set their own sender under the same settings section: an API mail provider or SMTP, with from-name customization
- Send a test email from the settings page to verify delivery before relying on notifications
- Emails are rate-limited per account to protect your sender reputation
Emails vs webhooks
Email is for humans; webhooks are for systems. If you automate fulfillment, do it from the signed webhook - never by parsing email.