Payments and email
Payments
PlexSub can reflect subscription and payment states from configured providers. The provider remains the legal and accounting source of truth; verify its data before cancelling access or making a financial decision.
What to decide first
- Which provider is authoritative for payment state.
- Which subscription states grant or remove access.
- How pending, failed, refunded, or cancelled payments are handled.
- Which portal information customers can see.
Payment variables
Keep payment-provider credentials and webhook secrets in protected configuration. Do not publish them in .env examples, screenshots, tickets, or logs.
SMTP email
Email can be used for invitations, notices, support, and account communication. Configure the SMTP host, port, sender identity, authentication, and TLS mode required by your provider.
Recommended email setup
- Configure a sender address that users recognise.
- Test delivery to an external mailbox.
- Verify spam and SPF/DKIM/DMARC configuration at the domain level.
- Keep message wording clear and avoid technical provider errors.
- Do not include passwords, tokens, or private data in emails.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Email is not sent | SMTP credentials or host incorrect | Check provider settings and application logs. |
| Messages arrive as spam | Sender domain is not authenticated | Configure SPF, DKIM, and DMARC. |
| Payment status is unexpected | Webhook or provider mapping issue | Check the provider, webhook secret, and diagnostics. |
| Customer has incorrect access | Subscription rules are unclear | Define which payment state is authoritative, then test with a safe account. |