Pay4All Shop - Simple order forms for products or events with TWINT Payment
| 开发者 | pay4all |
|---|---|
| 更新时间 | 2026年6月22日 19:40 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Drag-and-drop form builder with all common field types — default fields (first name, last name, e-mail, phone, address, etc.) are pre-translated in every activated language
- Products with photo, price, sale price, min/max/step quantities, short description
- Three product types — Physical (default), Virtual (downloadable file delivered after purchase), Ticket (one QR code per seat, sent in the order email)
- Out-of-stock flag — the product stays visible in the form but the quantity field is greyed out and disabled
- Categories with quantity rules — including minimum + multiple (e.g. wine sold by carton of 6, you can mix varieties as long as the total is 6, 12, 18…)
- Delivery methods — pickup, flat-rate, free, free over an amount, or no delivery; accepted payment methods are set per delivery so each delivery can expose its own payment choices to the customer
- Per-delivery customer-facing title and description in every activated language
- Tickets admin page — list every QR ticket, search by first/last name / city / e-mail, validate manually, export to CSV
- Public ticket validation page — the organizer scans the QR with any smartphone; the page shows a green Validate button if the seat is still available, or a red message with the date of the previous scan if already used
- Virtual file delivery — the file is stored in a private folder (
.htaccessprotected), the customer receives a one-time link valid for 60 days, served by the plugin's download endpoint - Order management — custom statuses, payment statuses, internal notes
- E-mails to the customer and the merchant — full content (subject, heading, intro, outro) editable per language
- CSV export of orders, filterable by date, form, status
- Privacy API integration for GDPR export/erase
- Honeypot anti-spam, nonces, server-side validation
- Internationalised (FR, DE, IT, EN)
- Pickup payment
- Cash on delivery
- Bank transfer with IBAN details
- TWINT manual (textual instructions to the customer)
https://api.qrserver.com/v1/create-qr-code/. The plugin server itself does not call this service — the request is made by the recipient when they open the email. The data passed to the service is only the ticket validation URL (your site domain + a random per-seat token).
Terms of service: https://goqr.me/api/
Privacy: https://goqr.me/api/#privacy
Use cases
- Winemakers selling by carton of 6
- Cheese makers selling by half-wheel
- Caterers with weekly order windows
- Local shops with pickup-only ordering
- Clubs taking online registrations with payment
- Concert organizers selling tickets with QR codes scanned at the door
- Digital sellers delivering PDFs, mp3s or course material as virtual products
安装:
- Upload the plugin to
/wp-content/plugins/pay4all-form/or install via Plugins › Add New. - Activate the plugin from the Plugins menu.
- Open Pay4All Shop in the admin sidebar.
- Create your categories, products, delivery methods, then a form.
- Copy the form shortcode into any page.
屏幕截图:
常见问题:
Do I need WooCommerce?
No. Pay4All Shop is standalone. It does not depend on WooCommerce in any way.
Can I sell wine by carton of 6, but let the customer mix varieties?
Yes — this is the core use case. Set the category to Minimum + multiple, with minimum 6 and multiple 6. The customer can pick any combination of bottles from that category as long as the total is 6, 12, 18, etc.
Does it support online payments?
The free version supports manual payments only (pickup, on delivery, bank transfer, TWINT instructions). Automated TWINT payments are available via Pay4All Pro.
Is the plugin GDPR-friendly?
Yes. Customer data is included in WordPress's Tools › Export / Erase Personal Data workflow.
Will my data be deleted if I uninstall?
No, unless you explicitly enable Réglages › Données › Supprimer les données lors de la désinstallation.
How do tickets work?
When you create a product of type Ticket and a customer orders N seats, the plugin generates N unique QR codes — one per seat. Each QR points to a public validation URL (/p4all-ticket/{slug}/{token}). The customer receives one e-mail with every QR embedded. At the door, the organizer scans a QR: the page shows a green Validate button when the ticket is still available, and a red message with the date of the previous scan if it has already been used. You can also validate tickets manually and search them by customer information from Pay4All Shop › Billets.
How do virtual products work?
When you create a product of type Virtual, you upload one file per product. The file is stored in wp-content/uploads/p4all-virtual/, protected by an automatically generated .htaccess (deny from all). After purchase, the customer's e-mail contains a one-time download link served by the plugin endpoint (?p4all_dl={token}). The link is valid for 60 days.
How does Out of stock work?
Tick the Rupture de stock checkbox on a product. The product stays visible in the form so the customer still sees what you usually offer, but the quantity field is greyed and disabled. A red badge labels the product as out of stock. Server-side validation rejects any tampered submission that tries to order an out-of-stock item.
更新日志:
- New product type Virtual — upload one downloadable file per product, customer receives a one-time link valid 60 days, served by the plugin's protected endpoint (files stored in a private folder with deny-all
.htaccess). - New product type Ticket — one QR code per seat ordered, sent in the order email, scannable from any smartphone, with a public validation page showing green (available) or red (already used).
- New admin page Pay4All Shop › Billets — list every QR ticket, search by first/last name / city / e-mail, validate manually, export to CSV.
- Out of stock flag on every product — product stays visible, quantity field is greyed and disabled, server-side rejects tampered orders.
- Default form fields (first name, last name, e-mail, phone, address, etc.) are now pre-translated in every activated language at form creation time.
- Per-delivery payment methods — accepted payment methods are now configured per delivery method (a delivery edit screen has a Modes de paiement acceptés section), so each delivery can show its own payment choices to the customer. Forms without any delivery still use the legacy per-form payment picker.
- Initial release.