Brand and delivery
Send certificates from your own address, domain, or provider
Choose how certificate email is sent and who it comes from: the shared Verifycate sender, your own verified domain, a connected provider such as Resend, Amazon SES, Postmark, SendGrid, Mailgun, or Cloudflare, or raw SMTP.
Certificate email should look like it came from the organisation that issued the certificate. Verifycate lets each workspace set its sender name, reply-to, CC, and BCC, then choose whether email goes through the shared Verifycate sender or a sender the workspace controls. Custom domains and providers are available on Pro.
How it works
Custom Email Senders
- 01
Set the sender identity
Choose the display name, from address, reply-to, and optional CC/BCC. The shared Verifycate sender is included on every plan; custom modes keep the same identity fields.
- 02
Verify your sending domain
For the custom-domain mode, publish the DKIM, SPF, and DMARC records shown in Settings, wait for DNS to propagate, and recheck the domain. Email falls back to the shared sender until the domain verifies.
- 03
Connect a provider or SMTP
Connect Cloudflare, Resend, Amazon SES, Postmark, SendGrid, or Mailgun with its credentials, or use raw SMTP. Send a test email to activate a customer-owned provider; credentials are encrypted at rest and never returned by the API.
- 04
Feed delivery events back
When a connected provider supports delivery webhooks, register Verifycate's webhook so delivered, bounced, and failed sends appear alongside the recipient and certificate activity.
Event examples
Where this workflow helps
- A university sends completion certificates from [email protected]
- A conference team sends from its event domain without changing its existing provider
- A training provider keeps using Postmark or Amazon SES and adds certificate email to the same sending account
For event organisers
See it in your event context
For universities
Universities and higher education
Issue verifiable certificates for courses, conferences, workshops, student activities, and microcredentials. Design a template, import a cohort, handle late requests and corrections, and give every student a public page they can keep.
See the event workflowFor event organisers
Conferences and events
Prepare and issue conference certificates by recipient group. Add event branding, sponsor details, QR verification, and public certificate pages.
See the event workflowFor training organisers
Training programmes and bootcamps
Prepare and issue certificates for bootcamps, cohort-based courses, and workplace training. Organise learner details, course information, and completion recognition in a batch.
See the event workflowFor event organisers
Webinars and workshops
Issue attendance or completion certificates for webinars and workshops. Upload the attendee list you have, or collect missing recipient details through the Issue Request Form (the glossary term is Certificate Request Form).
See the event workflowCommon questions
- Which email sender modes are available?
- Verifycate Sender (the shared platform sender), Custom Domain (your own verified domain), Connected Provider (Cloudflare, Resend, Amazon SES, Postmark, SendGrid, or Mailgun), and raw SMTP. The shared sender is included on every plan; the other modes are on Pro.
- Can we send from our own domain?
- Yes, on Pro. Add the domain in Settings, publish the DNS records shown, and recheck it. Verifycate sends from that domain once it verifies; until then, email falls back to the shared sender.
- Which providers can we connect?
- Cloudflare, Resend, Amazon SES, Postmark, SendGrid, and Mailgun, plus raw SMTP. A connected provider is activated with a test send, and its credentials are encrypted at rest.
- Can we use our existing SMTP server?
- Yes, on Pro. Enter the SMTP host, port, encryption mode, username, and password, then send a test email to activate it.
- What happens if our custom sender fails?
- Customer-owned providers and SMTP fail loudly with the provider's error, so you can fix the configuration. The custom-domain mode falls back to the shared sender until the domain verifies.
- Do custom email providers appear on the subprocessors page?
- No. When a workspace connects its own provider or SMTP server, that provider is selected and controlled by the customer, not by Verifycate. Its own terms and data processing apply.
Try custom email senders with your event
Start with 300 free credits. No card required.