Title: Blueforce Manual Payments for TWINT Author: blueforce Published: 4.7.2026 Last modified: 13.9.2026 --- Hae lisäosia ![](https://ps.w.org/blueforce-manual-payments-for-twint/assets/banner-772x250.png? rev=3595732) ![](https://ps.w.org/blueforce-manual-payments-for-twint/assets/icon.svg?rev=3595732) # Blueforce Manual Payments for TWINT [blueforce](https://profiles.wordpress.org/worshipper/) [Lataa](https://downloads.wordpress.org/plugin/blueforce-manual-payments-for-twint.1.6.8.zip) * [Tiedot](https://fi.wordpress.org/plugins/blueforce-manual-payments-for-twint/#description) * [Arvostelut](https://fi.wordpress.org/plugins/blueforce-manual-payments-for-twint/#reviews) * [Asennus](https://fi.wordpress.org/plugins/blueforce-manual-payments-for-twint/#installation) * [Kehitys](https://fi.wordpress.org/plugins/blueforce-manual-payments-for-twint/#developers) [Tuki](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/) ## Kuvaus 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. ## Kuvankaappaukset [⌊Checkout with the “Customer sends” flow – the customer sees your TWINT mobile number right away.⌉⌊Checkout with the “Customer sends” flow – the customer sees your TWINT mobile number right away.⌉[ Checkout with the “Customer sends” flow – the customer sees your TWINT mobile number right away. [⌊Thank-you page with payment instructions, a copy button for the order number and your TWINT QR code.⌉⌊Thank-you page with payment instructions, a copy button for the order number and your TWINT QR code.⌉[ Thank-you page with payment instructions, a copy button for the order number and your TWINT QR code. [⌊Checkout with the “I request” flow – the customer enters their TWINT mobile number.⌉⌊ Checkout with the “I request” flow – the customer enters their TWINT mobile number .⌉[ Checkout with the “I request” flow – the customer enters their TWINT mobile number. [⌊Gateway settings: flow, TWINT mobile number, account holder, QR image and additional notes.⌉⌊Gateway settings: flow, TWINT mobile number, account holder, QR image and additional notes.⌉[ Gateway settings: flow, TWINT mobile number, account holder, QR image and additional notes. [⌊Order screen with step-by-step instructions and the “Payment received – release order” button.⌉⌊Order screen with step-by-step instructions and the “Payment received– release order” button.⌉[ Order screen with step-by-step instructions and the “Payment received – release order” button. [⌊Customers can revisit the payment instructions at any time under My account – View order.⌉⌊Customers can revisit the payment instructions at any time under My account – View order.⌉[ Customers can revisit the payment instructions at any time under My account – View order. ## Asennus 1. Upload and activate the plugin. 2. Open WooCommerce Settings Payments TWINT. 3. Enable it, choose a workflow and configure it. ## UKK ### 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. ## Arvostelut ![](https://secure.gravatar.com/avatar/a1fea108dab67da64d7ac54f009eef6bcc8ff9707ec2a73f092e43c7e6ef525d? s=60&d=retro&r=g) ### 󠀁[Very easy to set up, works a treat!](https://wordpress.org/support/topic/very-easy-to-set-up-works-a-treat/)󠁿 [adih](https://profiles.wordpress.org/adih/) 11.8.2026 1 reply Easy to install, very well designed and seamlessly integrated into the shop system. [ Lue kaikki 1 arvostelua. ](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/) ## Avustajat & Kehittäjät “Blueforce Manual Payments for TWINT” perustuu avoimeen lähdekoodiin. Seuraavat henkilöt ovat osallistuneet tämän lisäosan kehittämiseen. Avustajat * [ blueforce ](https://profiles.wordpress.org/worshipper/) “Blueforce Manual Payments for TWINT” has been translated into 2 locales. Kiitoksia [kääntäjille](https://translate.wordpress.org/projects/wp-plugins/blueforce-manual-payments-for-twint/contributors) heidän työstään. [Käännä “Blueforce Manual Payments for TWINT” omalle kielellesi.](https://translate.wordpress.org/projects/wp-plugins/blueforce-manual-payments-for-twint) ### Oletko kiinnostunut kehitystyöstä? [Browse the code](https://plugins.trac.wordpress.org/browser/blueforce-manual-payments-for-twint/), check out the [SVN repository](https://plugins.svn.wordpress.org/blueforce-manual-payments-for-twint/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/blueforce-manual-payments-for-twint/) by [RSS](https://plugins.trac.wordpress.org/log/blueforce-manual-payments-for-twint/?limit=100&mode=stop_on_copy&format=rss). ## Muutosloki #### 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. #### 1.6.2 * New: dashboard widget showing the open TWINT payments (amount, customer reports, age of the oldest) and the payments received in the last 30 days, with a shortcut to the payments overview. #### 1.6.1 * Fixed: orders were marked as reminded even when the reminder email failed to send; they are now retried on the next run. * Fixed: auto-cancelling no longer cancels orders where the customer has reported” I have sent the payment” – those require manual review. #### 1.6.0 * New: ”TWINT payments” overview under the WooCommerce menu – all open (unpaid) TWINT orders with amount, customer, age, the matching instruction per flow and a one-click ”Payment received” button. * New: optional one-time payment reminder email for unpaid orders (days configurable; off by default). Customers who already reported their payment are not reminded. * New: optional auto-cancelling of unpaid TWINT orders after a configurable number of days (off by default); the stock is released automatically. * New: customers can report ”I have sent the payment” on the thank-you page and under My account. The report is shown on the order, in the payments overview and never changes the order status. * New: payment instructions (number/QR/reference) are also shown under My account View order while the payment is pending. * New: ”Paid with TWINT on [date]” note on PDF invoices (WooCommerce PDF Invoices& Packing Slips) – only when the order is actually paid. * New: in the ”I request” flow, the ”New order” admin email now contains the customer’s TWINT number, the amount and the reference. * New: the gateway settings only show the fields relevant to the selected flow. * Fixed: the phone-number hint in the block checkout appeared in German on non- German sites. * Fixed: the phone-number field in the block checkout overflowed the payment method box. * Fixed: the QR code in emails is now limited to a sensible size (email clients do not load the plugin stylesheet). * Changed: currency symbols in plain-text emails are no longer HTML-encoded. #### 1.5.1 * Fixed: the configuration notice (”Customer sends” flow active but no number or QR code set) stayed visible after switching to ”I request” until the next page load; the cached gateway settings are now refreshed on save. * Changed: `Plugin URI` now points to the plugin landing page instead of the GitHub repository. * Internationalisation: the bundled German translation is now split into de_DE ( German spelling) and de_CH (Swiss spelling). #### 1.5.0 – wordpress.org Welcome Release! * Internationalisation: the plugin now uses English source strings, with German, French (CH) and Italian (CH) shipped as proper translations. This lets translate. wordpress.org handle translations correctly – the previous German source strings prevented that. No functional changes. #### 1.4.3 * Wording: clarified that the plugin itself needs no TWINT API key or acquiring contract, while shop operators remain responsible for their own TWINT, bank and merchant terms for commercial use. * Removed ”TWINT logo” phrasing from older changelog notes to avoid trademark ambiguity; the plugin icon is a custom Blueforce design. * Updated the translation template and metadata to the current version. * Hardening: the selected workflow (send/request) is normalised to a known value on load and save; block checkout data is sanitised before it is passed to the front end. * Packaging/CI: the build script now verifies that development, test, repo and WordPress.org asset folders never end up in the distributed plugin ZIP; PHP lint is limited to the actual plugin files. * Cleanup: added uninstall.php so deleting the plugin removes its stored gateway settings (order data is kept). * Consistency: aligned the license notation between the plugin header and readme, and updated remaining internal doc comments to the current plugin name. * Privacy/hardening: in the ”Customer sends” workflow the block checkout no longer stores a customer phone number server-side, even if a manipulated client submits the field – matching the classic checkout and the stated privacy behaviour. #### 1.4.2 * Coding standards: renamed the gateway class to use the plugin prefix (BF_TWINT_Gateway). * Header: shortened the plugin description to under 140 characters, added ”Requires Plugins: woocommerce”, and updated ”WC tested up to”. * Packaging: include composer.json in the distributed plugin; keep GitHub-only docs (README.md, CHANGELOG.md) out of the ZIP. * No functional changes. #### 1.4.1 * Security/hardening: escape settings field output late with wp_kses_post() (tooltip and description HTML in the QR image field); removed the corresponding phpcs: ignore annotations. No functional changes. #### 1.4.0 * Renamed to ”Blueforce Manual Payments for TWINT” and prepared for the WordPress. org plugin directory. * Removed the previous GitHub-based update mechanism; the plugin no longer makes external calls. * No functional changes to checkout, workflows or privacy. #### 1.3.0 * Order snapshot: workflow, number, account holder, QR image and notes are frozen per order – thank-you page, email and admin stay correct even if the settings are changed later. * Block checkout: TWINT is now correctly hidden for foreign currencies (as in the classic checkout). * Privacy: customer number is included in data export/erasure; privacy policy snippet added. * Admin notice for incomplete configuration; real plain-text email; centralised phone validation/normalisation. * Accessibility improvements; inline styles moved to CSS; ”Mark as paid” button restricted to authorised roles, with a logged note. * CI: PHP lint, WordPress Coding Standards and ZIP build test. #### 1.2.0 * ”Mark as paid” button in the order screen: release a TWINT order as paid with one click. * French and Italian translations – including block checkout. * Copy button for the order number on the thank-you page (fewer typos in the TWINT message). * TWINT is only shown when the shop currency is CHF (filter ”bf_twint_is_available” to override). #### 1.1.2 * Security: additional capability check (manage_woocommerce) when loading the admin scripts. #### 1.1.1 * Plugin icon shown in the plugin list. * English translations (en_GB/en_US) added for the new admin texts (QR image selection). #### 1.1.0 * TWINT QR image: select directly from the media library via a button (instead of typing a URL), with preview. #### 1.0.2 * Block checkout: payment method icon next to the method name and required-field marker (”*”) on the mobile number. #### 1.0.1 * Internal improvements. #### 1.0.0 * Initial release. ## Metatiedot * Version **1.6.8** * Last updated **4 viikkoa sitten** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.0.7** * PHP version ** 7.4 or higher ** * Languages * [English (US)](https://wordpress.org/plugins/blueforce-manual-payments-for-twint/), [German](https://de.wordpress.org/plugins/blueforce-manual-payments-for-twint/) ja [German (Switzerland)](https://de-ch.wordpress.org/plugins/blueforce-manual-payments-for-twint/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/blueforce-manual-payments-for-twint) * Tags * [manual payment](https://fi.wordpress.org/plugins/tags/manual-payment/)[payment gateway](https://fi.wordpress.org/plugins/tags/payment-gateway/) [Switzerland](https://fi.wordpress.org/plugins/tags/switzerland/)[twint](https://fi.wordpress.org/plugins/tags/twint/) [woocommerce](https://fi.wordpress.org/plugins/tags/woocommerce/) * [Edistynyt näkymä](https://fi.wordpress.org/plugins/blueforce-manual-payments-for-twint/advanced/) ## Arvosanat 5 out of 5 stars. * [ 1 5-star review ](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/reviews/) ## Avustajat * [ blueforce ](https://profiles.wordpress.org/worshipper/) ## Tuki Onko sinulla jotain sanottavaa? Tarvitsetko apua? [Tukifoorumi](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/)