harish282

<p>NiyiGuard hardens WordPress at the <strong>application layer</strong>: login abuse, accountability, file integrity, browser security headers, optional rate limits, and WooCommerce-specific threats. It <strong>complements</strong> your host firewall, CDN, or WAF — it does not replace them.</p>
<p>Source code and issue tracker: https://github.com/harish282/securepress</p>
<h4>Why install NiyiGuard?</h4>
<ul>
<li><strong>Self-hosted</strong> — security data stays on your server; no NiyiGuard account and no usage telemetry to the author.</li>
<li><strong>One dashboard</strong> — enable or disable modules (authentication, audit log, integrity, headers, rate limits, WooCommerce protection).</li>
<li><strong>For store owners</strong> — reduce fake checkouts, cart and coupon abuse, registration spam, and Store API abuse when WooCommerce is active.</li>
<li><strong>For developers</strong> — protect custom <code>admin-post</code> handlers, forms, and REST routes with the <strong>Security SDK</strong> (CSRF, rate limits, signed URLs, route guards).</li>
<li><strong>Fully free</strong> — no license key, beta trial, or paywalled module in 0.1.0.</li>
</ul>
<h4>What makes it different?</h4>
<p>Many security plugins offer two-factor auth, lockouts, headers, or malware scanning. NiyiGuard does not claim to be the only plugin with those features. It stands out in three ways:</p>
<ol>
<li><strong>Developer SDK</strong> — middleware-style helpers for <strong>your</strong> code paths, not only wp-admin toggles.</li>
<li><strong>WooCommerce abuse pipelines</strong> — checkout, cart, registration, and Store API protection in the same package as audit logging and login hardening.</li>
<li><strong>Privacy-first</strong> — no license server and no analytics to the author (see Privacy section below).</li>
</ol>
<p>Longer positioning notes and reusable marketing copy: <code>docs/WHY_NIYIGUARD.md</code>.</p>
<h4>Features included (0.1.0)</h4>
<ul>
<li><strong>Authentication hardening</strong> — login lockouts (IP and username), TOTP and email two-factor authentication, recovery codes, session tracking with remote revoke, and new-device suspicious-login email alerts.</li>
<li><strong>Security headers</strong> — HSTS, Content-Security-Policy, X-Frame-Options, Referrer-Policy, Permissions-Policy, and X-Content-Type-Options (each header can be toggled).</li>
<li><strong>Audit log</strong> — logins, plugin changes, role changes, selected option changes, file editor use, and WooCommerce-related actions. Admin list UI, detail view, retention, and scheduled pruning.</li>
<li><strong>File integrity monitoring</strong> — WordPress.org core checksum comparison, plugin manifest diff scans, suspicious PHP heuristics, and optional themes/uploads scopes (scheduled scans).</li>
<li><strong>Rate limiting</strong> — optional global throttling for front-end, AJAX, wp-login, and REST API traffic (wp-admin dashboard loads excluded by default).</li>
<li><strong>WooCommerce Protection</strong> — checkout, cart, registration, and Store API pipelines (velocity limits, honeypots, disposable-email checks, fraud scoring, coupon abuse). Requires WooCommerce.</li>
<li><strong>CSRF middleware and SDK</strong> — nonce verification for custom routes, forms, and REST handlers you register.</li>
<li><strong>Signed URLs</strong> — time-limited HMAC links for downloads, invites, and sensitive actions.</li>
<li><strong>Login URL disguise</strong> — optional custom login path instead of <code>wp-login.php</code> (off by default; test on staging first).</li>
<li><strong>Safe mode</strong> — emergency bypass via <code>NIYIGUARD_SAFE_MODE</code> in <code>wp-config.php</code> without changing saved settings.</li>
<li><strong>Health diagnostics</strong> — hooks, database tables, and module state on an admin screen.</li>
<li><strong>MU loader helper</strong> — optional must-use loader for earlier bootstrap in the request lifecycle.</li>
</ul>
<p>The <strong>NiyiGuard <span aria-hidden="true" class="wp-exclude-emoji">→</span> Dashboard</strong> includes optional links to leave a WordPress.org review or support development (Ko-fi). Neither is required.</p>
<h4>Developer APIs</h4>
<p>The <code>Security</code> facade provides route guards, CSRF fields, rate limiters, signed URLs, and related helpers. Documented in <code>docs/USAGE.md</code>. Middleware applies to <strong>routes you protect</strong> — it is not automatic site-wide protection for every WordPress hook. Before production, follow <code>docs/STAGING_TEST_PLAN.md</code>.</p>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.4+</li>
<li>PHP 8.2+</li>
<li>MySQL 5.7+ or MariaDB 10.3+ (standard WordPress database)</li>
</ul>
<h3>Privacy</h3>
<p>NiyiGuard processes security-related data on your WordPress server (IP addresses, user agents, user IDs, audit events, session metadata, and similar fields when features are enabled). It does not sell personal data or include advertising trackers.</p>
<p><strong>Third-party service</strong></p>
<ul>
<li><strong>WordPress.org Core Checksums API</strong> (<code>https://api.wordpress.org/core/checksums/1.0/</code>) — used for core file integrity checks (WordPress version and locale only; responses may be cached about 12 hours).</li>
</ul>
<p><strong>Email</strong></p>
<p>Optional security emails (two-factor codes, suspicious-login alerts) use WordPress <code>wp_mail()</code> and your site’s mail configuration.</p>
<p><strong>Optional donations</strong></p>
<p>If you use the dashboard Ko-fi link, payment and any data you provide are handled by Ko-fi under their terms, not by NiyiGuard.</p>
<p>Full details: <code>docs/PRIVACY.md</code> in the plugin folder, and the Privacy section below.</p>


NiyiGuard

Self-hosted WordPress security: 2FA, lockouts, audit log, integrity, headers, rate limits, WooCommerce protection, and SDK. Free.

onlinecity

<p>Send SMS notifications for WooCommerce orders, create SMS campaigns, manage contacts, and add two-factor authentication – powered by GatewayAPI.com.</p>
<h3>📝 Description</h3>
<p>GatewayAPI for WordPress is a powerful SMS plugin that combines WooCommerce transactional SMS notifications with a high-performance campaign and contact management system.</p>
<p>The plugin allows you to automatically send SMS messages when WooCommerce orders change status, as well as create and send personalized SMS campaigns to large contact lists.</p>
<p>You can also add an extra layer of security to your WordPress site with SMS-based two-factor authentication, helping protect your login process with verification codes sent directly to your mobile device.</p>
<p>Version 2 is a complete rewrite of the plugin, with a strong focus on performance, reliability, and modern WordPress standards.</p>
<p>All SMS messages are delivered via GatewayAPI.com, one of Europe’s leading SMS gateways.</p>
<h3>⭐ Main Features</h3>
<h4>🛒 WooCommerce SMS Notifications</h4>
<ul>
<li>Send automatic SMS messages based on WooCommerce order status changes</li>
<li>Separate message templates for customer and internal recipients</li>
<li>Fully configurable per order status</li>
<li>Supports all standard WooCommerce order statuses</li>
</ul>
<h4>🔐 Two-Factor Authentication</h4>
<ul>
<li>Add an extra layer of security to your WordPress login</li>
<li>SMS-based verification codes sent automatically during login</li>
<li>Can be limited to specific roles and phone countries</li>
<li>Works with standard WordPress authentication</li>
<li>Uses GatewayAPI’s reliable SMS delivery</li>
</ul>
<h4>📢 SMS Campaigns & Broadcasts</h4>
<ul>
<li>Send SMS campaigns to large contact lists</li>
<li>High throughput and stable delivery using Action Scheduler</li>
<li>Designed to work reliably even on shared web hosting</li>
<li>Background processing</li>
</ul>
<h4>📇 Contact & List Management</h4>
<ul>
<li>Manage contacts directly in WordPress</li>
<li>Import and export contacts using CSV files</li>
<li>Store custom fields per contact</li>
<li>Reusable contact lists for campaigns</li>
<li>Use contact fields for mail-merged SMS content</li>
</ul>
<h4>✉️ Personalized Message Templates</h4>
<ul>
<li>Mail-merge support for campaigns and WooCommerce messages</li>
<li>Use dynamic placeholders such as customer data, order data, and custom fields</li>
<li>Supports both GSM and Unicode SMS</li>
<li>Configurable sender ID per message</li>
</ul>
<h4>🧩 Frontend Shortcodes</h4>
<ul>
<li>Signup: Allow users to subscribe to your SMS lists directly from your website.</li>
<li>Update Profile: Enable users to update their contact details and group subscriptions.</li>
<li>Unsubscribe: Provide a simple way for users to opt-out of SMS communications.</li>
<li>Send SMS: Enable SMS sending from the frontend (e.g. for internal tools).</li>
</ul>
<h4>🚀 Built for Reliability & Scale</h4>
<ul>
<li>Uses Action Scheduler (the same job system used by WooCommerce)</li>
<li>Non-blocking background processing</li>
<li>Suitable for very large campaigns (100,000+ recipients)</li>
<li>No PHP timeouts or long-running requests</li>
</ul>
<h3>⚠️ Coming from v1.x? Some features are gone</h3>
<p>The following features are not part of this plugin anymore:</p>
<ul>
<li>Receiving or processing incoming SMS messages</li>
<li>Contact Form 7-integration</li>
</ul>
<p>These features had very low usage and were removed to simplify the plugin. If you need this, consider the legacy version of the plugin (any version before 2.0).</p>
<h3>🌍 About GatewayAPI.com</h3>
<ul>
<li>Founded in 1999</li>
<li>One of Europe’s leading SMS providers</li>
<li>Offices in Copenhagen, Odense, and Aalborg, Denmark</li>
<li>Hundreds of millions of SMS messages delivered yearly</li>
<li>No subscriptions – pay only for what you send</li>
<li>Fast and reliable SMS delivery worldwide</li>
</ul>
<h3>🔧 Installation</h3>
<ol>
<li>Create a free account at https://gatewayapi.com/</li>
<li>Install and activate the plugin</li>
<li>Go to GatewayAPI <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings</li>
<li>Add your API Token from your GatewayAPI.com account</li>
<li>Play around! Send a test campaign or setup a WooCommerce Order hook</li>
</ol>
<h3>🚀 Getting Started</h3>
<h4>🛍️ WooCommerce Notifications</h4>
<p>After installation, you can enable SMS notifications per WooCommerce order status.<br />
Each status can send messages to customers, internal recipients, or both.</p>
<p>Place a test order to confirm everything is working as expected.</p>
<h4>📨 Campaign Messaging</h4>
<p>You can create SMS campaigns without WooCommerce:</p>
<ul>
<li>Import contacts via CSV or add them manually</li>
<li>Organize contacts into lists</li>
<li>Create a personalized SMS campaign</li>
</ul>
<h4>🔐 Two-Factor Authentication</h4>
<p>To add SMS-based two-factor authentication to your WordPress site:</p>
<ul>
<li>Go to GatewayAPI <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Two-Factor</li>
<li>Enable two-factor authentication</li>
<li>Configure which user roles should use two-factor authentication</li>
<li>Optionally limit to specific phone countries for security</li>
<li>Set a grace period if needed</li>
</ul>
<h3>🧩 Shortcodes</h3>
<p>The plugin provides shortcodes to integrate SMS features into your frontend.</p>
<h4>📝 Common Attributes</h4>
<ul>
<li>action: (required) One of signup, update, unsubscribe, send_sms.</li>
<li>recaptcha: Set to 1 to enable Google reCAPTCHA (must be configured in settings).</li>
<li>embed_css: Set to 1 to embed basic styling for the form.</li>
<li>groups: Comma-separated list of group/tag IDs to target.</li>
<li>allowed_countries: Comma-separated list of country codes (e.g., 45,44).</li>
</ul>
<h4>➕ Signup Form</h4>
<p>[gatewayapi action=”signup” groups=”1,2,3″]</p>
<h4>🔄 Update Profile</h4>
<p>[gatewayapi action=”update”]</p>
<h4>❌ Unsubscribe</h4>
<p>[gatewayapi action=”unsubscribe”]</p>
<h4>✉️ Send SMS</h4>
<p>[gatewayapi action=”send_sms” groups=”1″]</p>
<p>Security Warning: The send_sms action allows sending SMS messages from your frontend. This can be dangerous if left open to the public as it could be abused to send spam or drain your GatewayAPI credits.</p>
<p>We strongly recommend combining this with a security system, such as:<br />
* Placing the shortcode on a password-protected page.<br />
* Restricting access to specific user roles using a membership plugin.<br />
* Always enabling recaptcha=”1″ to prevent automated abuse.</p>
<h3>❓ Frequently Asked Questions</h3>
<h4>Can this plugin handle very large SMS campaigns?</h4>
<p>Yes. Campaigns are processed using Action Scheduler, ensuring stable delivery, high throughput, and retries — even on shared hosting environments.</p>
<h4>Does this plugin support personalized SMS messages?</h4>
<p>Yes. You can use dynamic placeholders from contacts and WooCommerce orders to send fully personalized, mail-merged SMS messages.</p>
<h4>Is WooCommerce required?</h4>
<p>WooCommerce is only required for order-based SMS notifications.<br />
Campaign messaging and contact management work without WooCommerce.</p>
<h3>🔗 External services</h3>
<p>This plugin connects to the GatewayAPI.com service to send SMS messages. This external service is required for the plugin’s primary functionality, which is delivering transactional and campaign SMS messages.</p>
<p>When sending an SMS, the plugin transmits the recipient phone number, message content, and related metadata (such as sender ID) to GatewayAPI.com. For WooCommerce notifications, order-related data may be used to generate the message content before it is sent.</p>
<p>No data is sent to GatewayAPI.com unless an SMS is actively being sent by the site administrator or triggered by configured WooCommerce events.</p>
<p>This service is provided by GatewayAPI ApS.</p>
<p>Privacy policy, terms and conditions, data processing agreement, and security certifications (including ISAE 3000 and ISAE 3402) are available at:<br />
https://gatewayapi.com/security-and-compliance/</p>
<h3>📋 Changelog</h3>
<h4>2.1.4</h4>
<ul>
<li>Improved UI for tag dropdowns when there are many items.</li>
</ul>
<h4>2.1.3</h4>
<ul>
<li>New bulk actions for all contacts matching current filters: Delete/deactivate/activate contact + add/remove tag.</li>
<li>Contacts list UI update, more sleek import/export buttons.</li>
</ul>
<h4>2.1.2</h4>
<ul>
<li>Improved contact import: Papa Parse CSV parser with auto-delimiter detection and auto-created meta fields from unknown columns.</li>
<li>Fallback support: Support for our previous (<v2.0) CSV format support.</li>
</ul>
<p><h4>2.1.1</h4>
</p>
<ul>
<li>Bugfix: The recipient tags were not properly sent to the campaign creation UI.</li>
</ul>
<h4>2.1.0</h4>
<ul>
<li>New feature: Shortcodes for signup, updating contact details, and unsubscription.</li>
<li>New feature: Shortcode for sending SMS from the frontend (use with caution and combine with security-system).</li>
<li>Bugfix: Contacts filtering by tag didn’t work.</li>
</ul>
<h4>2.0.8</h4>
<ul>
<li>The migration tool should now be available to all users of the 1.x-versions, as some were missing it.</li>
</ul>
<h4>2.0.7</h4>
<ul>
<li>Tool for easy and automatic migration of old contacts, contact fields and contact groups included.</li>
<li>Automatically migrates and uses old OAuth key.</li>
</ul>
<h4>2.0.5</h4>
<ul>
<li>Bugfix: For users upgrading from 1.x, a missing capability upgrade made the plugin unavailable until deactivate + reactivate.</li>
</ul>
<h4>2.0.4</h4>
<ul>
<li>Two-factor authentication has been re-added to the plugin.</li>
</ul>
<h4>2.0.2-2.0.3</h4>
<ul>
<li>No changes. These versions exist because we have been working on automating release processes.</li>
</ul>
<h4>2.0.1</h4>
<ul>
<li>Minor modifications to ensure best-practices as per WordPress guidelines.</li>
</ul>
<h4>2.0.0</h4>
<ul>
<li>Complete rewrite of the plugin!</li>
</ul>
<h4>1.8.3</h4>
<ul>
<li>Compability up to WordPress 6.3.1.</li>
</ul>
<h4>1.8.2</h4>
<ul>
<li>Bugfix: Built in shortcode defaulted to the posts title as the name of the new recipient. Now defaults to ”, as expected.</li>
</ul>
<h4>1.8.1</h4>
<ul>
<li>Bugfix: Built in shortcode for signup did not work properly, when allowing the user to select groups.</li>
</ul>
<h4>1.8.0</h4>
<ul>
<li>Support for using our GatewayAPI.eu-setup!</li>
<li>Bugfix: 2FA login security could fail on PHP 7.4+.</li>
</ul>
<h4>1.7.6</h4>
<ul>
<li>Bugfix: Fixing that GatewayAPI Shortcode for signup had stopped saving some meta-fields since 1.7.2.</li>
</ul>
<h4>1.7.5</h4>
<ul>
<li>Bugfix: Default country code did not apply correctly in the country drop downs.</li>
</ul>
<h4>1.7.4</h4>
<p>Compability with Contact Form 7.</p>
<ul>
<li>Bugfix: Signup via Contact Form 7 works again (upgraded to being compatible with CF7’s newer window.fetch based approach of AJAX).</li>
<li>Bugfix: Notices in CF7-integration (PHP) and a typo, causing an exception in frontend JS on CF7-forms.</li>
</ul>
<h4>1.7.3</h4>
<p>Bugfix release.</p>
<ul>
<li>Bugfix: Saving recipient details using the UI and via Excel-importer, works properly again.</li>
<li>Bugfix: SMS Reply-feature works again.</li>
</ul>
<h4>1.7.2</h4>
<p>This release strengthens the overall security, thanks to input from an external security audit.</p>
<p>We highly recommend upgrading to this version, as it hardens the security of our plugin, especially on WordPress-installation with multiple users<br />
which may have users of lower roles than editor.</p>
<ul>
<li>Consistent use of nonce’s in AJAX requests, to prevent CSRF and prevent privilege escalation.</li>
<li>Enforce correct roles for various actions, preventing potential privilege escalation.</li>
<li>Improved sanitizing, validation and escaping of input and output.</li>
<li>All PHP-files are now secured from direct access.</li>
<li>Refactored function prefixes from <code>gwapi_</code>, <code>_gwapi_</code> and <code>_gatewayapi_</code> to <code>gatewayapi_</code> only.</li>
</ul>
<h4>1.7.1</h4>
<ul>
<li>Bugfix: Notifications were not sent.</li>
</ul>
<h4>1.7.0</h4>
<ul>
<li>New: Notification module: Receive SMS-notifications when various actions occur in WordPress
<ul>
<li>BETA: Please get in touch if you have ideas/suggestions for improving this feature.</li>
</ul>
</li>
<li>New: Default country code field setting (previously all country selectors defaulted to +45/Denmark).</li>
<li>New: Programmer actions <code>gwapi_form_subscribe</code> and <code>gwapi_form_unsubscribe</code> added. The first is triggered when new recipients complete signup via<br />
our shortcode-forms and the latter on unsubscription via the shortcode-forms.</li>
<li>Optimization: Removed various unneeded dependencies.</li>
<li>Danish translation updated, including the notification-module.</li>
<li>Readme updated to inform about notification-module and other text improvements.</li>
</ul>
<h4>1.6.9</h4>
<ul>
<li>New! Create Notifications to automatically notify recipients by SMS when a WP action is executed.</li>
</ul>
<h4>1.6.8</h4>
<ul>
<li>Bugfix: Prefix wasn’t specified for all instances of db_table usages.</li>
</ul>
<h4>1.6.7</h4>
<ul>
<li>Bugfix: Previously imported recipients was prevented from being re-imported if they had been deleted.</li>
</ul>
<h4>1.6.6</h4>
<ul>
<li>Bugfix: While using recipients import, group recipients was not counted correctly after the import was completed.</li>
</ul>
<h4>1.6.5</h4>
<ul>
<li>Improved: Import of recipients optimized.</li>
</ul>
<h4>1.6.4</h4>
<ul>
<li>Compatible with WordPress 5.5</li>
<li>Improved: Integration with Contact Form 7 now supports shortcode for mandatory fields</li>
<li>Tweak: Updated UI and descriptions.</li>
</ul>
<h4>1.6.3</h4>
<ul>
<li>Compatible with WordPress 5.4</li>
<li>New! Recipient groups can now default to unchecked when using short-code</li>
<li>Tweak: Minor updates to UI.</li>
</ul>
<h4>1.6.2</h4>
<ul>
<li>Tweak: The frontend forms now use regular SMS instead of Display SMS for two-factor, as requested by multiple users.</li>
<li>Bugfix: When using tags, the list of tags sent to GatewayAPI could end in a situation, with the same tag-data repeated.</li>
</ul>
<h4>1.6.1</h4>
<ul>
<li>Removed URL in two-factor SMS as it was unnecessary and caused SMS’es to be blocked by GatewayAPI’s new link-scanner.</li>
</ul>
<h4>1.6.0</h4>
<ul>
<li>New! Custom encoding for SMS’es, allowing SMS’es with emojis and other special characters.
<ul>
<li>UI which detects what encoding should be used, always recommending the cheapest option (ie. most characters per SMS).</li>
<li>API-method <code>gwapi_send_sms</code> has new argument for setting encoding.</li>
<li>Fully backwards-compatible, defaulting to standard-encoding.</li>
</ul>
</li>
<li>Compatible with WordPress 5.1</li>
</ul>
<h4>1.5.2</h4>
<ul>
<li>Compable with WordPress 5.0.3.</li>
<li>Fix: Excel-export of recipients did not work unless “SMS Inbox” was enabled.</li>
<li>Fix: Notices in Excel-export.</li>
</ul>
<h4>1.5.1</h4>
<ul>
<li>Updated Danish translations (primarily the two-factor settings and frontend).</li>
<li>Fix: Our shortcode had unintentionally been renamed. We now support both <code>[gwapi]</code> and <code>[gatewayapi]</code>.</li>
<li>Fix: Two-factor-module caused fatal error on PHP 5. Also fixed general notices in two-factor module.</li>
<li>Fix: Two-factor module caused fatal error when creating new WordPress-users.</li>
</ul>
<h4>1.5.0</h4>
<ul>
<li>New! Two-factor security upgrade to your WordPress! (optional)</li>
<li>New! Blacklisting of phone numbers.</li>
<li>Improved: Searching recipients by phone number works.</li>
<li>Improved: Better support for 10.000+ recipients + a progress bar for showing progress.</li>
</ul>
<h4>1.4.2</h4>
<ul>
<li>Recipients:
<ul>
<li>Added option to blacklist phone numbers.</li>
<li>Added support for searching recipients list by phone number (previously only by name).</li>
<li>Added drop down on recipients list, for filtering by group.</li>
</ul>
</li>
<li>Fix: Improved handling of huge lists of recipients (ie. 1.000+ recipients in one SMS)</li>
</ul>
<h4>1.4.1</h4>
<ul>
<li>Fix: List of countries is now always correctly parsed, even when the JSON-file (which is fetched via AJAX) does not have right mime-type.</li>
</ul>
<h4>1.4.0</h4>
<p>Note: <strong>v1.4.0 may break your Countact Form 7-forms containing GatewayAPI-fields</strong>, as the shortode-syntax has slightly changed for most of our fields. We needed to do this change to fix multiple bugs and inconsistencies. Please re-add the GatewayAPI-fields to your Contact Form 7-forms when updating the plugin.</p>
<ul>
<li>
<p>Contact Form 7:</p>
<ul>
<li>Ability to send SMS’es from the frontend.</li>
<li>Updating a subscriber: Forms now only updates groups specifically selected for the form.</li>
<li>Bugfixes and code cleanup, improved shortcode syntax.</li>
</ul>
</li>
<li>
<p>Complete user guide for the system (available online).</p>
</li>
<li>Export of recipients to Excel and CSV-formats.</li>
</ul>
<h4>1.3.3</h4>
<ul>
<li>Contact Form 7: Added support for forms which also contained a reCaptcha-field.</li>
<li>Code cleanup</li>
</ul>
<h4>1.3.2</h4>
<ul>
<li>Bugfix: A menu item had gone missing in the backend.</li>
</ul>
<h4>1.3.1</h4>
<ul>
<li>New UI for creating automated actions. Currently supports “autoreply” based on keyword.</li>
</ul>
<h4>1.3.0</h4>
<ul>
<li>Support for receiving SMS’es added, including setup-wizard and inbox.</li>
</ul>
<h4>1.2.3</h4>
<ul>
<li>Bugfix: The new verification SMS for Contact Form 7 had a typo, breaking verification SMS’es.</li>
<li>Missing translations: The popup-messages related to verification were not translated to danish.</li>
</ul>
<h4>1.2.2</h4>
<ul>
<li>Better international phone numbers support: Prefixed 0’s in the phone number itself (between country prefix and phone number) is now correctly working.</li>
</ul>
<h4>1.2.1</h4>
<ul>
<li>User synchronization:
<ul>
<li>No longer requires a country code meta field, instead allowing a default country code when this value is missing.</li>
<li>Now possible to trigger a “one time” synchronization.</li>
</ul>
</li>
<li>Contact Form 7:
<ul>
<li>Now possible to send an SMS-reply on form success automatically.</li>
<li>SMS-validation for signup, before allowing the form to submit successfully.</li>
<li>Bugfix: Validation now works for all GatewayAPI-fields.</li>
</ul>
</li>
</ul>
<h4>1.2.0</h4>
<ul>
<li>Contact Form 7: Integration supporting signup, update and unsubscribe forms for frontend. Two-factor flow possible for update-flow.</li>
</ul>
<h4>1.1.6</h4>
<ul>
<li>Bugfix: Safari-specific issue with SMS-counter.</li>
<li>Bugfix: Hidden required fields  …</li>
</ul>


GatewayAPI

Send SMS notifications for WooCommerce orders, create SMS campaigns, manage contacts, and add two-factor authentication - powered by GatewayAPI.com.

NiyiGuard vs GatewayAPI