AhaPay Buy Now Pay Later vs Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

AhaPay integrates with WooCommerce to provide flexible payment options for your customers. The plugin allows shoppers to split their payments into 4 or 7 installments automatically, with no hidden fees and 0% interest on 4-payment plans. Requirements WordPress 5.4 or higher WooCommerce 4.8 or higher PHP 7.4 or higher OpenSSL PHP extension SSL certificate installed on your domain (for secure transactions) Configuration Basic Settings Enable/Disable – Turn the payment method on or off Title – The payment method title shown to customers Description – The payment method description shown to customers Environment – Choose between Sandbox (testing) and Production API Key – Enter your AhaPay API key Minimum Amount – Set the minimum order amount for AhaPay availability Display Settings Product Label – Enable/disable BNPL information on product pages Product Label Text – Customize the BNPL message Product Label Color – Set the background color for labels Product Label Text Color – Set the text color for labels Features Seamless integration with WooCommerce checkout Automatic order status updates Real-time payment verification Custom product page badges and banners Responsive payment modal Support for both desktop and mobile devices Order status checking in admin panel Sandbox environment for testing Detailed payment status tracking Support for refunds Payment Flow Customer selects AhaPay at checkout Order is created and customer is redirected to AhaPay Customer completes payment setup with AhaPay Order status is automatically updated Customer is redirected back to your store Order Statuses PAYMENT_SUCCESSFUL – Payment completed CANCELLED – Payment cancelled by customer UNAVAILABLE – Payment failed PAYMENT_IN_PROGRESS – Payment pending REFUNDED – Payment refunded Support For support or questions, please contact AhaPay support team or visit your AhaPay merchant dashboard. External services This plugin connects to the AhaPay API to process Buy Now Pay Later payments and handle order status updates. It sends the following data when processing payments or checking status: – Order ID and transaction details – API key for authentication – Refund requests with order information Data is sent securely via HTTPS to AhaPay’s servers only when necessary for payment processing or status verification. This service is provided by AhaPay: Terms of Service, Privacy Policy. Development This plugin uses webpack to build JavaScript and CSS assets. Build Process Install dependencies: npm install Build assets: npm run build (or npm run dev for development) Source files are located in the blocks/ directory. Built files are in assets/blocks/. The source code is publicly available in this repository for review and modification. 1.0.0 Initial release Basic payment integration Order status management Product page integration Admin interface Sandbox/Production environments License This plugin is licensed under the terms of use provided by AhaPay. Customize Payment Fields CSS You can add custom CSS that will be applied specifically to AhaPay’s payment fields on the checkout page from the plugin settings in the WordPress admin. How to update the CSS In WordPress admin go to: WooCommerce → Settings → Payments. Find “AhaPay Buy Now Pay Later” in the list and click Manage (or click the Settings link). Scroll down to the setting named “Additional CSS for Payment Fields”. Paste your CSS into the textarea and click Save changes. How the plugin applies your CSS The plugin stores the textarea content and adds it as inline CSS attached to the plugin stylesheet handle ahapaybuynowpaylater-block-style. The payment fields output by the gateway are wrapped in a container with the class .ahapay-payment-fields, so we recommend scoping your rules under that selector to avoid affecting other parts of your site. The plugin will strip surrounding tags if you paste them by accident, and it sanitizes the textarea input on save. If you need to override existing rules, use specificity or !important as needed. Quick verification example Paste the following CSS into the “Additional CSS for Payment Fields” textarea and save. Then open your checkout page (or the block checkout) and you should see a green dashed border, a small badge that reads “ADDITIONAL CSS APPLIED”, and visible styling changes for the title, subtitle and progress bar. This is a visual test to confirm the inline CSS is applied. `css /* Visual test for Additional CSS for Payment Fields */ .ahapay-payment-fields { border: 3px dashed #27ae60 !important; background: rgba(39, 174, 96, 0.04) !important; padding: 12px !important; position: relative !important; border-radius: 6px !important; } /* Badge so you can clearly see the CSS is applied */ .ahapay-payment-fields::before { content: “ADDITIONAL CSS APPLIED”; position: absolute; top: -12px; right: 8px; background: #27ae60; color: #ffffff; font-weight: 700; font-size: 11px; padding: 3px 8px; border-radius: 3px; box-shadow: 0 1px 2px rgba(0,0,0,0.15); z-index: 9999; } .ahapay-payment-fields .ahapay-title { color: #e91e63 !important; font-size: 18px !important; font-weight: 700 !important; } .ahapay-payment-fields .ahapay-subtitle { color: #555 !important; font-style: italic !important; } .ahapay-payment-fields .ahapay-progress-bar { background: #eee !important; height: 12px !important; border-radius: 12px !important; margin: 10px 0 !important; } .ahapay-payment-fields .ahapay-progress { width: 75% !important; height: 100% !important; background: linear-gradient(90deg,#e91e63,#ff8a80) !important; border-radius: 12px !important; } .ahapay-payment-fields .ahapay-timeline div { display: inline-block !important; background: #fff8e1 !important; padding: 6px 8px !important; margin-right: 6px !important; border-radius: 4px !important; font-weight: 600 !important; } ` Small examples Change the title color only: css .ahapay-payment-fields .ahapay-title { color: #0066cc !important; } Hide the timeline if it conflicts with your theme: css .ahapay-payment-fields .ahapay-timeline { display: none !important; } Troubleshooting If you don’t see the changes after saving the CSS, try these steps: Ensure the AhaPay payment method is enabled (WooCommerce → Settings → Payments → AhaPay). Clear any caching on your site (plugin cache, server cache, CDN) and your browser cache. Confirm you’re viewing a checkout page that loads the plugin styles (block checkout or classic checkout). If you use a custom checkout template, ensure the ahapay-payment-fields wrapper is present in the markup. Use !important or increase specificity if your theme’s CSS is overriding the rules. Security and best practices The textarea is intended for admin use only. Avoid pasting untrusted CSS/JS — the plugin strips tags but does not execute arbitrary JS. Keep rules scoped (start with .ahapay-payment-fields) to avoid unintentionally affecting other areas of your site.

Easily improve site security with WordPress Hardening, Two-Factor Authentication (2FA), Login Protection, Vulnerability Detection and SSL certificate. Really simple, Effective and Performant WordPress Security Really Simple Security is the most lightweight and easy-to-use security plugin for WordPress. It secures your WordPress website with SSL certificate generation, including proper 301 https redirection and SSL enforcement, scanning for possible vulnerabilities, Login Protection and implementing essential WordPress hardening features. We believe that security should have the absolute minimum effect on website performance, user experience and maintainability. Therefore, Really Simple Security is: Lightweight: Every security feature is developed with a modular approach and with performance in mind. Disabled features won’t load any redundant code. Easy-to-use: 1-minute configuration with short onboarding setup. Security Features Easy SSL Migration Migrates your website to HTTPS and enforces SSL in just one click. 301 redirect via PHP or .htaccess Secure cookies Let’s Encrypt: Install an SSL Certificate if your hosting provider supports manual installation. Server Health Check: Your server configuration is every bit as important for your website security. WordPress Hardening Tweak your configuration and keep WordPress fortified and safe by tackling potential weaknesses. Prevent code execution in the uploads folder Prevent login feedback and disable user enumeration Disable XML-RPC Disable directory browsing Username restrictions (block ‘admin’ and public names) and much more.. Vulnerability Detection Get notified when plugins, themes or WP core contain vulnerabilities and need appropriate action. Login Protection Allow or enforce Two-Factor Authentication (2FA) for specific user roles. Users receive a two-factor code via Email. Improve Security with Really Simple Security Pro Protect your site with all essential security features by upgrading to Really Simple Security Pro. Advanced SSL enforcement Mixed Content Scan & Fixer. Detect files that are requested over HTTP and fix them to HTTPS, both Front- and Back-end. Enable HTTP Strict Transport Security and configure your site for the HSTS Preload list. Firewall Really Simple Security Pro includes a performant and efficient WordPress firewall, to stop bots, crawlers and bad actors with IP and username blocks. 404 blocking – Blocks crawlers as they trigger unusual numbers of 404 errors. Region blocking – Only allow/block access to your site from specific regions. Automated and customisable Firewall rules. IP blocklist and allowlist. Security Headers Security headers protect your site visitors against the risk of clickjacking, cross-site-forgery attacks, stealing login credentials and malware. Independent of your Server Configuration, works on Apache, LiteSpeed, NGINX, etc. Protect your website visitors with X-XSS Protection, X-Content-Type-Options, X-Frame-Options, a Referrer Policy and CORS headers. Automatically generate your WordPress-tailored Content Security Policy. Vulnerability Measures When a vulnerability is detected in a plugin, theme or WordPress core you will get notified accordingly. With Vulnerability Measures, you can configure simple but effective measures to make sure that a critical vulnerability won’t remain unattended. Force update: An update process will be tried multiple times until it can be assumed development of a theme or plugin is abandoned. You will be notified during these steps. Quarantine: When a plugin or theme can’t be updated to solve a vulnerability, Really Simple Security can quarantine the plugin. Advanced Site Hardening Choose a custom login URL Automated File Permissions check and fixer Rename and randomize your database prefix Change the debug.log file location to a non-public folder Disable application passwords Control admin creation Disable HTTP methods, reducing HTTP requests Login Protection Secure your website’s login process and user accounts with powerful security measures. Two-Step verification (Email login) 2FA (two factor authentication) with TOTP Passwordless login with passkey login Enforce strong passwords and frequent password change Limit Login Attempts With Limit Login Attempts you can configure a threshold to temporarily or permanently block IP addresses or (non-existing) usernames. You can also throw a CAPTCHA after a failed login (hCaptcha or Google reCaptcha) Access Control Restrict access to your site for specific regions. Add specific IP addresses or IP ranges to the Blocklist or Allowlist. Useful Links Documentation Security Definitions Translate Really Simple Security Issues & pull requests Feature requests Love Really Simple Security? If you want to support the continuing development of this plugin, please consider buying Really Simple Security Pro, which includes some excellent security features and premium support. About Really Simple Plugins Our mission is to make complex WordPress requirements really easy. Really Simple Security is developed by Really Simple Plugins. For generating SSL certificates, Really Simple Security uses the le acme2 PHP Let’s Encrypt client library, thanks to ‘fbett’ for providing it. Vulnerability Detection uses WP Vulnerability, an open-source initiative by Javier Casares. Want to join as a collaborator? We’re on GitHub as well!