rapls

<p>Thanks Mail for Stripe is a lightweight plugin that automatically sends customized thank-you emails to customers after they complete a purchase through Stripe Payment Links. Perfect for digital product sales, software licensing, and service businesses.</p>
<p>👉 <strong>Setup guide & developer’s notes:</strong> <a href="https://raplsworks.com/thanks-mail-for-stripe/" rel="nofollow ugc">Why I built this and how to set up Stripe webhooks</a></p>
<h4>No external services required – works directly with Stripe Webhooks</h4>
<p>This plugin receives Stripe webhook events directly and sends emails using WordPress’s built-in mail function. No Zapier, Make, or other third-party automation services needed.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Automatic Email Sending</strong> – Sends thank-you emails automatically via Stripe Webhook</li>
<li><strong>Multi-language Support</strong> – Up to 10 customizable email templates with locale settings</li>
<li><strong>Smart Language Detection</strong> – Automatically detects customer language from Payment Link ID or locale</li>
<li><strong>Customizable Templates</strong> – Fully customizable email subject and body with placeholders</li>
<li><strong>Custom Sender Settings</strong> – Set custom From email address and sender name</li>
<li><strong>Duplicate Prevention</strong> – Built-in idempotency prevents sending duplicate emails</li>
<li><strong>Test Email Function</strong> – Send test emails to verify your settings before going live</li>
<li><strong>Email Log</strong> – View history of sent emails in the admin panel</li>
<li><strong>Secure Webhook Verification</strong> – Validates Stripe webhook signatures (HMAC-SHA256)</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Customer makes a purchase via your Stripe Payment Link</li>
<li>Stripe sends a webhook event to your WordPress site</li>
<li>Plugin verifies the webhook signature for security</li>
<li>Plugin detects customer language based on Payment Link ID</li>
<li>Thank-you email is sent to the customer using wp_mail()</li>
<li>Transaction is logged to prevent duplicate sends on retries</li>
</ol>
<h4>Use Cases</h4>
<ul>
<li>Digital product sales (software, ebooks, courses)</li>
<li>Software license key distribution (manual follow-up)</li>
<li>Service booking confirmations</li>
<li>Donation thank-you messages</li>
<li>Any Stripe Payment Links checkout</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.0 or higher</li>
<li>PHP 7.4 or higher</li>
<li>Stripe account with Payment Links</li>
<li>SSL certificate (HTTPS) – required for webhooks</li>
<li>SMTP plugin recommended for reliable email delivery</li>
</ul>
<h4>Email Sender Best Practices</h4>
<p><strong>Important:</strong> Always use your own domain email address as the “From Email” setting.</p>
<ul>
<li><strong>Good:</strong> info@yoursite.com, support@yoursite.com</li>
<li><strong>Bad:</strong> yourname@gmail.com, yourname@yahoo.com</li>
</ul>
<p>Using Gmail or other free email services as the sender will cause delivery failures due to SPF/DKIM/DMARC authentication. Your server is not authorized to send emails on behalf of Gmail.</p>
<p>You CAN use any email address (including Gmail) for the “Reply-To” setting – this only affects where replies go, not email deliverability.</p>
<h4>Recommended SMTP Plugins</h4>
<p>For reliable email delivery, we recommend using an SMTP plugin:</p>
<ul>
<li>WP Mail SMTP</li>
<li>Post SMTP</li>
<li>FluentSMTP</li>
</ul>
<p>These plugins send emails through a proper SMTP server instead of PHP’s mail() function, improving deliverability.</p>
<h4>Test vs Live Mode</h4>
<p>Remember to update your settings when switching from test to live mode:</p>
<ul>
<li><strong>Webhook Signing Secret</strong> – Test and Live have different secrets (whsec_…)</li>
<li><strong>Payment Link IDs</strong> – Test and Live have different IDs (plink_…)</li>
<li><strong>Webhook Endpoints</strong> – Register endpoints in both Test and Live mode in Stripe Dashboard</li>
</ul>
<h4>Security Best Practices</h4>
<ul>
<li>The plugin verifies Stripe webhook signatures using HMAC-SHA256</li>
<li>Webhook requests are validated within a 5-minute tolerance window</li>
<li>Session IDs are stored to prevent duplicate email sends</li>
<li>All settings are properly sanitized and escaped</li>
</ul>
<h4>Available Filter Hooks</h4>
<p>The plugin provides filter hooks for customization:</p>
<ul>
<li><code>tmfs_email_headers</code> – Modify email headers before sending</li>
<li><code>tmfs_email_subject</code> – Customize email subject</li>
<li><code>tmfs_email_body</code> – Customize email body</li>
<li><code>tmfs_detect_language</code> – Override language detection logic</li>
</ul>
<h4>Example: Add CC to emails</h4>
<pre><code>add_filter( 'tmfs_email_headers', function( $headers, $to, $lang, $session_id ) {
    $headers[] = 'Cc: sales@example.com';
    return $headers;
}, 10, 4 );
</code></pre>
<h4>Example: Custom language detection</h4>
<pre><code>add_filter( 'tmfs_detect_language', function( $lang, $session ) {
    // Custom logic based on session data
    if ( strpos( $session['customer_details']['email'], '.jp' ) !== false ) {
        return 'ja';
    }
    return $lang;
}, 10, 2 );
</code></pre>
<h4>Database Table</h4>
<p>The plugin creates a table <code>{prefix}stm_sent_emails</code> to track sent emails:</p>
<ul>
<li><code>id</code> – Auto-increment ID</li>
<li><code>session_id</code> – Stripe Checkout Session ID (unique)</li>
<li><code>email</code> – Customer email address</li>
<li><code>lang</code> – Detected language (ja/en)</li>
<li><code>product_name</code> – Product name (if available)</li>
<li><code>amount</code> – Purchase amount</li>
<li><code>sent_at</code> – Timestamp when email was sent</li>
</ul>
<h4>Troubleshooting Webhook Issues</h4>
<p>If webhooks aren’t working, check these common issues:</p>
<ol>
<li><strong>SSL Certificate</strong> – Stripe requires HTTPS for webhooks</li>
<li><strong>Webhook URL</strong> – Make sure the URL is correct and accessible</li>
<li><strong>Signing Secret</strong> – Verify you’re using the correct secret for test/live mode</li>
<li><strong>Server Firewall</strong> – Some hosts block requests from overseas IPs</li>
<li><strong>Security Plugins</strong> – May block REST API endpoints</li>
<li><strong>WAF Rules</strong> – Server-level WAF may block webhook requests</li>
</ol>
<p>Check Stripe Dashboard > Developers > Webhooks for detailed error logs.</p>
<h3>Data & Privacy</h3>
<p>This plugin stores email delivery logs in your WordPress database to prevent duplicate sending and allow administrators to verify delivery history. No data is transmitted to external services by this plugin.</p>
<h4>What Data Is Stored</h4>
<p>The plugin stores the following data in a custom database table (<code>{prefix}stm_sent_emails</code>):</p>
<ul>
<li><code>session_id</code> – Stripe Checkout Session ID (used as unique key for duplicate prevention)</li>
<li><code>email</code> – Customer email address (to confirm which customer received the email)</li>
<li><code>lang</code> – Detected language code, ja or en (to record which template was used)</li>
<li><code>product_name</code> – Product name (reserved for future use)</li>
<li><code>amount</code> – Purchase amount and currency (for administrator reference)</li>
<li><code>sent_at</code> – Timestamp when the email was sent</li>
</ul>
<p>Additionally, plugin settings (webhook secret, email templates, Payment Link IDs, etc.) are stored in the <code>wp_options</code> table under the key <code>stm_settings</code>.</p>
<h4>Purpose</h4>
<ul>
<li><strong>Duplicate prevention</strong> – Stripe may retry webhook events; the session ID prevents sending the same email twice</li>
<li><strong>Delivery confirmation</strong> – Administrators can verify that emails were sent to the correct address</li>
<li><strong>Customer support</strong> – Transaction reference for handling customer inquiries</li>
</ul>
<h4>Data Retention</h4>
<ul>
<li>Email logs are stored indefinitely by default</li>
<li>Administrators can manually delete individual records via database access</li>
<li><strong>All data (logs and settings) is automatically removed when uninstalling the plugin</strong> via the WordPress admin</li>
</ul>
<h4>External Services</h4>
<ul>
<li>This plugin receives incoming webhook events from Stripe – it does not make outbound API calls to Stripe</li>
<li>No customer data is sent to any third-party service by this plugin</li>
<li>Emails are sent using WordPress’s built-in <code>wp_mail()</code> function (delivery depends on your server or SMTP plugin configuration)</li>
</ul>
<h4>GDPR Considerations</h4>
<ul>
<li>Customer email addresses are stored for the legitimate business purpose of preventing duplicate emails and maintaining delivery records</li>
<li>You should disclose this data storage in your site’s privacy policy</li>
<li>Data can be exported or deleted upon customer request via direct database access</li>
</ul>


Thanks Mail for Stripe

Automatically send thank-you emails when Stripe Payment Links purchases are completed. Supports Japanese and English with customizable templates.

crgeary

<p>Please refer to the Github repository <a href="https://github.com/crgeary/wp-jamstack-deployments" rel="nofollow ugc">crgeary/wp-jamstack-deployments</a> for usage instructions, and for support.</p>


JAMstack Deployments

This plugin does some really great stuff to trigger a deploy on Netlify (or other JAMstack hosts) based on activity on the WordPress website. 

Most often this would be used for headless WordPress, but since it's using build hooks (which essentially just tell the JAMstack host to process the build) it could be utilized for more than just headless CMS applications.

The setup was straightforward, and aided by screenshots. I've not explored using JAMstack providers other than Netlify for setup, but for Netlify this config setup procedure was very simple. 

One thing I'd love to see is a manual override option: sometimes I want to make a few quick changes in a row on my WP site that would (by default) trigger a build for each one. I'd like to be able to manually tell this plugin "don't trigger now" without having to manually deactivate it, and then when all changes are made I could deploy the changes all at once. This would save me some build minutes at Netlify. 

I'd envision this as a button in the top bar beside (or nested under) the deploy button that essentially allows "pausing" of deployments.

All told, great plugin that does exactly what it says!

Works fantastically with Netlify!

The perfect bridge between two awesome stacks: LAMP and JAMstack.
Great work, thanks for sharing!

Excellent Work

A WordPress plugin for JAMstack deployments on Netlify (and other platforms).

Thanks Mail for Stripe vs JAMstack Deployments