| 开发者 | anishamdi |
|---|---|
| 更新时间 | 2026年11月17日 22:32 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
_takrg_risk. Nothing is blocked, nothing is hidden. Safe to try on a live shop.20 123 456, +216 20123456, 00216-20-123-456 and ٢٠ ١٢٣ ٤٥٦ are the same customer. A "default country" setting reads numbers typed without a country code.*@example.com or +21620*.Only if you choose so, and only cash on delivery. The default action only adds an order note and the meta _takrg_risk, so a wrong match never stops a sale. The other two actions remove or refuse Cash on Delivery for that customer; every other payment method keeps working.
It targets repeat fake and refused cash-on-delivery orders: once an order is marked as refused, the same phone number or e-mail is recognised on the next order, in any phone format. It is not a general firewall: it does not score IP addresses, devices or card payments.
Yes, for cash on delivery. The list is filled automatically from refused orders, and you can also add or remove numbers and e-mails by hand or by CSV (import and export are free).
Same phone number (in any format, see above) or same e-mail address. A person who gives a new e-mail but the same phone number is still recognised.
Cash on Delivery is removed through the woocommerce_available_payment_gateways filter, which the Store API also uses, and it is refused again when the order is submitted. In the block checkout the customer sees the message when they try to place the order; in the classic checkout the payment method disappears (or the notice appears) as soon as the phone number or the e-mail is entered, through a one-line inline script that loads no file and contacts no server.
Change the order out of the counted status and its record is removed. You can also delete a record, or every record of a phone number or e-mail, in the settings page.
Yes. WooCommerce > Refusal Guard > Import CSV. One row per refusal: phone,email (the header row is optional). Numbers without a country code use the default country. Export gives the same columns plus order, source and date.
do_action( 'takrg_signal', $phone, $email, $order_id, 'takeed' ) records a refusal signal from another plugin. The function takrg_record_refusal( $phone, $email, $order_id, $source ) does the same.apply_filters( 'takrg_refusal_count', $count, $phone, $email ) adds signals to the count (for example, Takeed confirmation results).apply_filters( 'takrg_is_risky', $risky, $count, $phone, $email ) overrides the decision.apply_filters( 'takrg_counted_statuses', $statuses ) changes the statuses that count as a refusal.do_action( 'takrg_refusal_recorded', $id, $row ) and do_action( 'takrg_order_tagged', $order, $count ).A circuit breaker against mistakes. If more than half of the checkout attempts of the last hour were restricted (with at least 5 attempts, and one customer counted once), something is wrong, for example a rule that is too wide. The plugin then only tags orders, shows a notice in the admin and sends the administrator an e-mail (through your own mail setup). The restriction comes back only when you press "Turn protection back on". The attempt that trips the breaker is still restricted; from the next checkout on, Cash on Delivery is available again.
The order goes through. Any error while checking a customer lets the order continue, and the error is written to the activity log.
No. Sites that already used 1.0 keep the action they chose and stay in Live mode. Only new installations start in Test mode.
No. There are no external HTTP calls, no tracking and no analytics.