Blueforce Manual Payments for TWINT
Manual TWINT payment method for WooCommerce – the plugin needs no TWINT API or acquiring contract. Payments are confirmed by hand.
Solid choice
Blueforce Manual Payments for T… is a solid plugin choice in 2026, with a few things worth checking first. Is rated 5/5 and was last updated 2 weeks ago, and scores 66/100 on our health check.
- Actively developed — last update 2 weeks ago
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Blueforce Manual Payments f… stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| manual payment | #96 |
| payment gateway | >100 |
| Switzerland | #34 |
| twint | #7 |
| woocommerce | >100 |
Rating breakdown
★★★★★★★★★★ 5 from 1 reviews
About Blueforce Manual Payments for TWINT
From the official readme · v1.6.8Description
This plugin adds a TWINT payment method to WooCommerce. The plugin itself needs no TWINT API, no acquiring contract and no payment service provider – it uses the manual TWINT process (send or request money by mobile number) and is therefore suited to small shops, clubs and sole traders. It runs on any hosting: no PHP extensions, no certificate, PHP 7.4 or newer. You remain responsible for complying with your own TWINT, bank and business terms for commercial use.
TWINT does not offer its payment API publicly. An automated integration is only possible through a TWINT acquiring contract or a payment service provider. This plugin deliberately takes the manual route, so you can start without a TWINT integration contract while still meeting your own TWINT and bank conditions.
Please note: private TWINT accounts have a monthly limit on money received (mostly CHF 4’000), so check your own limit with your bank.
Two workflows
- Customer sends: The customer is shown your TWINT mobile number and, optionally, your QR code. They send the amount using the order number as the message.
- I request: The customer enters their TWINT mobile number; you request the amount in the TWINT app.
In both cases the order is set to “On hold” and the incoming payment is confirmed by hand.
Features
- Classic and block checkout
- Optional TWINT QR code on the thank-you page, in the order email and under My account
- “TWINT payments” overview: all open payments at a glance, with one-click release
- Optional one-time payment reminder email for unpaid orders
- Optional auto-cancelling of unpaid orders after a configurable number of days (stock is released)
- Customers can report “I have sent the payment” – shown on the order and in the payments overview
- “Paid with TWINT” note on PDF invoices (with WooCommerce PDF Invoices & Packing Slips)
- HPOS compatible
- Translation-ready; German (Germany and Switzerland) included, French and Italian via translate.wordpress.org
- No external dependencies, no tracking, no phone-home calls
- Runs on any hosting: no PHP extensions, no shell access, no certificate, PHP 7.4 or newer
- Site Health checks (Tools > Site Health): shop currency, payment details and scheduled tasks
- Run log for auto-cancelling and payment reminders (WooCommerce > Status > Logs, source “bf-twint”)
Privacy
In the “I request” workflow the plugin stores the TWINT mobile number provided by the customer as order metadata (_bf_twint_customer_phone) in order to request the payment via the TWINT app. This number is included in the WooCommerce/WordPress data export and erasure tools. No data is sent to third parties and no external services are contacted; payment reconciliation is done manually in the TWINT app.
Installation
- Upload and activate the plugin.
- Open WooCommerce → Settings → Payments → TWINT.
- Enable it, choose a workflow and configure it.
Frequently asked questions
Do I need a contract with TWINT?
The plugin itself needs no TWINT API key, acquiring contract or payment service provider – it uses the manual TWINT process. Please note that the terms of your TWINT, bank and merchant account still apply: if you accept payments commercially, check your own TWINT and bank conditions for business use.
Is the payment verified automatically?
No. The incoming payment is checked in the TWINT app and the order is set to “Processing” by hand.
Do I need to set up a cron job for the reminder or auto-cancelling?
No. Both run via WP-Cron and manage themselves: as soon as you enter a number of days, the schedule is created; setting it back to 0 (or deactivating the plugin) removes it again. On low-traffic sites WP-Cron runs with the next visit, so the exact time of day may vary – which does not matter for reminders and cancellations.
When exactly are reminders sent and orders cancelled?
The plugin checks twice a day. A customer receives the reminder once, after the configured number of days without payment – and never after reporting “I have sent the payment”. Auto-cancelling triggers after its own configured number of days and releases the reserved stock. Both options are off by default.
Is this plugin official TWINT software?
No. It is an independent community project by Blueforce Digital Solutions and is not affiliated with TWINT AG. “TWINT” is a registered trademark of TWINT AG and is used here only to describe compatibility.
What personal data is stored?
Only in the “I request” workflow: the TWINT mobile number the customer enters at checkout (as order metadata, used solely to request the payment). It is included in the WordPress data export and erasure tools; a suggested privacy policy snippet is available under Settings → Privacy. In the “Customer sends” workflow, no personal payment data is collected.
Changelog
Renamed and prepared for the WordPress.org plugin directory; the GitHub-based update mechanism was removed (no more external calls). No functional changes.
1.6.8
- New: three checks under Tools > Site Health (shop currency, payment details, scheduled tasks), so a silent misconfiguration becomes visible where WordPress collects such findings.
- New: an admin notice when the shop currency is not CHF. Until now the payment method simply disappeared from the checkout without explanation.
- New: every auto-cancel and reminder run is logged under WooCommerce > Status > Logs (source “bf-twint”), including which orders were cancelled.
1.6.7
- Security: hardening release. Stricter validation of customer input at checkout and safer handling of redirects. No configuration changes needed, updating is recommended.
- Privacy: order notes no longer contain the full customer phone number or email address. The full values stay in the order itself and remain covered by the personal-data export and erasure.
- Fixed: uninstalling the plugin now also removes the review-prompt counter and the per-user dismissal.
1.6.6
- New: an unobtrusive review prompt on the “TWINT payments” screen, shown only after you have released at least 10 payments with the plugin. It offers “Write a review”, “I already did” and “Maybe later”, is dismissed per user and never appears anywhere else in the admin.
- Changed: the “no-referrer” policy on the TWINT QR image now also applies in emails, not just on the thank-you page.
- Changed: tested up to WooCommerce 11.0.
1.6.5
- Hardening: the checkout now safely ignores a manipulated array payload for the TWINT number instead of triggering a PHP error.
- Hardening: the TWINT QR image is loaded with “no-referrer” so the order page URL cannot leak to an external image host.
- Changed: a customer’s “I have sent the payment” report is now clearly labelled as unverified on the order and in the payments overview, to avoid it being mistaken for a confirmed payment.
- Changed: invalid TWINT numbers in the block checkout now return a proper validation error (HTTP 400) instead of a generic server error.
- Changed: the permission error when releasing an order now returns HTTP 403.
- Fixed: plain-text order emails (customer and admin) no longer show HTML-encoded characters in the payment details.
- Fixed: a negative number of days in the reminder/auto-cancel settings now disables the feature instead of being turned into a positive value.
- Removed: unused internal helper methods (dead code from before 1.6.3).
1.6.4
- Fixed: reporting “I have sent the payment” no longer exempts an order from auto-cancelling forever. Auto-cancelling now applies a short grace period from the report (3 days, filter “bf_twint_claim_grace_days”) and then proceeds, so a merely claimed but unpaid order can no longer block the stock indefinitely.
- Fixed: the thank-you page no longer shows the payment instructions once the order has been paid or cancelled.
- Fixed: on multisite, uninstalling now cleans up settings and cron events on all sites, not just the first 100.
- Changed: the “WooCommerce required” admin notice is now only shown to users who can manage plugins.
- Docs: clarified that the “bf_twint_is_available” filter receives the gateway instance or null (block checkout fallback).
1.6.3
- Fixed: auto-cancelling could stop working permanently. Orders with a customer payment report were skipped only after loading, so once enough of them piled up they filled every batch and newer unpaid orders were never cancelled. They are now excluded from the query itself.
- Fixed: payment reminders could be missed on shops with many open TWINT orders, for the same reason.
- Fixed: the cron events are now removed reliably when the plugin is deactivated, even if WooCommerce was deactivated first.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Blueforce Manual Payments for… alternatives
All manual payment plugins →
FAQ
Blueforce Manual Payments for TWINT: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 29, 2026
Is Blueforce Manual Payments for T… free?
Yes. Blueforce Manual Payments for T… is free to download and use from the official WordPress.org plugin directory.
Is Blueforce Manual Payments for T… safe to use in 2026?
Blueforce Manual Payments for T… is a solid plugin choice in 2026, with a few things worth checking first. Is rated 5/5 and was last updated 2 weeks ago, and scores 66/100 on our health check.
How many websites use Blueforce Manual Payments for T…?
Blueforce Manual Payments for T… is active on <10 WordPress websites and has been downloaded 729 times since it launched in July 2026. It was downloaded 220 times in the last 30 days.
Does Blueforce Manual Payments for T… work with WordPress 7.1?
Blueforce Manual Payments for T… is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Blueforce Manual Payments for T… need?
Blueforce Manual Payments for T… requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Blueforce Manual Payments for T… last updated?
The latest version, 1.6.8, was released on September 13, 2026 (2 weeks ago).
Who makes Blueforce Manual Payments for T…?
Blueforce Manual Payments for T… is developed and maintained by blueforce.
What are the best alternatives to Blueforce Manual Payments for T…?
The most popular alternatives to Blueforce Manual Payments for T… are Advance Bank Payment Transf… (1K+ installs), Payment Gateway for Paybox… (200+ installs) and Halk Bank Payment Gateway F… (100+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
