Title: Blueforce Manual Payments for TWINT Author: blueforce Published: July 4, 2026 Last modified: July 4, 2026 --- Search plugins ![](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 By [blueforce](https://profiles.wordpress.org/worshipper/) [Download](https://downloads.wordpress.org/plugin/blueforce-manual-payments-for-twint.1.5.0.zip) * [Details](https://wordpress.org/plugins/blueforce-manual-payments-for-twint/#description) * [Reviews](https://wordpress.org/plugins/blueforce-manual-payments-for-twint/#reviews) * [Installation](https://wordpress.org/plugins/blueforce-manual-payments-for-twint/#installation) * [Development](https://wordpress.org/plugins/blueforce-manual-payments-for-twint/#developers) [Support](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/) ## Description 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. 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. #### 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 and in the email * HPOS compatible * Translation-ready; German, English, French (CH) and Italian (CH) translations included * No external dependencies, no tracking, no phone-home calls ### 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 1. Upload and activate the plugin. 2. Open WooCommerce Settings Payments TWINT. 3. Enable it, choose a workflow and configure it. ## FAQ ### 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. ### 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. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Blueforce Manual Payments for TWINT” is open source software. The following people have contributed to this plugin. Contributors * [ blueforce ](https://profiles.wordpress.org/worshipper/) [Translate “Blueforce Manual Payments for TWINT” into your language.](https://translate.wordpress.org/projects/wp-plugins/blueforce-manual-payments-for-twint) ### Interested in development? [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). ## Changelog #### 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 (fr_CH) and Italian (it_CH) 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. ## Meta * Version **1.5.0** * Last updated **8 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.0** * PHP version ** 7.4 or higher ** * Tags * [manual payment](https://wordpress.org/plugins/tags/manual-payment/)[payment gateway](https://wordpress.org/plugins/tags/payment-gateway/) [Switzerland](https://wordpress.org/plugins/tags/switzerland/)[twint](https://wordpress.org/plugins/tags/twint/) [woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/blueforce-manual-payments-for-twint/advanced/) ## Ratings No reviews have been submitted yet. [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/) ## Contributors * [ blueforce ](https://profiles.wordpress.org/worshipper/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/blueforce-manual-payments-for-twint/)