AhaPay Buy Now Pay Later
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.
Translate WordPress with GTranslate
Translate WordPress with GTranslate plugin uses Google Translate AI translation service to translate wordpress site with Google power and make it multilingual. With 103 available languages your site will be available to more than 99% of internet users. Our paid versions are fully SEO compatible which will increase your international traffic and sales. This translate plugin is a budget multilingual WordPress solution which combines automatic and human translations to save money and is easy to implement. GTranslate is a leading website translation services provider since 2008, it moves away the language barriers. Compared to other translation plugins for WordPress, we use cloud based approach which does not slow down your website. In addition to that, we can offer complete SEO features based on sub-domains with our paid options, which can make your website appear in search engines in different languages which will increase your international traffic and sales. In our paid versions we DO NOT limit the number of words or the number of translated pageviews. You DO NOT pay additionally for automatic translations. Please use GTranslate Support for your questions and support requests! We are multilingual! Please check our FAQ to get quick answers. Free translation service: permitted use Under the GTranslate Terms of Service, the free translation service is available for personal, educational, internal testing, nonprofit and governmental purposes, provided the use does not directly generate revenue from the service. Nonprofit use must further nonprofit activities; governmental use includes public institutions and other public-sector entities. Commercial or revenue-generating use requires an applicable paid subscription. This free-service restriction does not apply to free trials of paid subscriptions. These service conditions do not change the WordPress plugin code’s GPLv2-or-later license. Features Automatic machine translation Translate website on the fly Translate posts and pages Translate categories and tags Menus and widgets translation Themes and plugins translation Right to left language support Google Translate website translator widget alternative Auto-switch language based on browser defined language Available styles Float, Dropdown, Flags, Flags with dropdown, Nice dropdown with flags, Flags with language names, Flags with language codes, Language names, Language codes, Globe, Popup Floating language selector WooCommerce shop translation Multilingual language names in native alphabet Alternative flags for Quebec, Canada, USA, Brazil, Mexico, Argentina, Colombia Lazy loading for language flags and js libraries to boost performance Lightweight vanilla javascript without dependencies Forum Support Paid Features Multilingual SEO – Enable search engine indexing Neural machine translations with human level translation quality Increase traffic and AdSense revenue Search engine friendly (SEF) URLs Yoast SEO compatible – translate meta keywords, meta description, schema.org data structures, translate sitemaps WooCommerce compatible – translate products, schema.org data structures You can have sub-directory (example.com/es/) or sub-domain (es.example.com) URL structure URL Translation aka slug translation is possible (example.com/about-us → example.es/sobre-nosotros) Add hreflang tags for translated alternatives You can manually correct translations In context translation interface (make corrections without losing the context) Meta data translation (meta keywords, meta description) Translating schema.org microdata for better search engine appearance Seamless updates (cloud service updated on our side – SaaS, you do not need to worry about backups on your side) JSON format translation Translate WooCommerce emails AMP translation (Accelerated Mobile Pages translation) Image localization – Media translation Translation Proxy (aka Translation Delivery Network) Centralized Translation Cache – We revise and improve translations over time Language Hosting (example.fr) User Dashboard with Analytics Live Chat Support See also If you are looking for unlimited, high-quality automatic translations, check out TranslateX – an automatic translation API offering unlimited translation for your website or application. We also offer integration plugins: TranslateX for Loco Translate – integrate TranslateX API directly into Loco Translate for seamless, unlimited automatic translations. TranslateX for TranslatePress – bring unlimited automatic translation to TranslatePress using TranslateX API. These solutions make it easy to supercharge your WordPress multilingual setup with TranslateX’s secure and affordable API. GTranslate WordPress Demo Watch GTranslate Tour Edit Translations Demo (paid) External services This plugin uses external services to load the language selector and obtain automatic translations. GTranslate widget delivery When the widget loads, the visitor’s browser requests its files from cdn.gtranslate.net over HTTPS. GTranslate, Inc. provides the widget, which connects the visitor’s browser to the translation service. Google translation requests When page translation is requested, the widget sends page text for translation from the visitor’s browser to translate-pa.googleapis.com over HTTPS. Google processes these translation requests. The content sent is the page text being translated. Loading widget files and requesting translations are separate network operations. These requests also expose standard connection and HTTP request information, such as the visitor’s IP address and browser headers, to the receiving service. Provider processing and retention practices are described in the applicable policies; browser-based translation does not mean that no data leaves the browser or that providers retain no data. If you configure a paid translation proxy service, translated versions of your website are processed and served through GTranslate’s cloud infrastructure according to your service configuration. GTranslate, Inc.: Terms of Service, Privacy Policy Google: Terms of Service, Privacy Policy Review these services when updating your website’s privacy information and configuring any consent or content-security controls. The plugin requires access to the relevant external services for translation to work.