TAFI - Págalo Relax -- WordPress 插件

开发者	tafitechsys
更新时间	2026年8月29日 07:50
PHP版本:	8.0 及以上
WordPress版本:	7.1
版权:	GPL-2.0-or-later
版权网址:	版权信息

TAFI Pay lets your customers buy now and pay in installments without a credit card, using a WhatsApp-based confirmation flow operated by TAFI Tech in Panama. How it works:

The customer selects "Pay with TAFI" at checkout
The customer enters a Panamanian mobile phone number
TAFI sends a credit request to the customer through WhatsApp
The customer accepts within 2 minutes and the payment is confirmed automatically
Your store receives a webhook notification and processes the order

Features:

Native integration with WooCommerce, no extra code required
Simple setup: only an API Key and Merchant ID are needed
Sandbox and production environments
Automatic notifications via webhook
High-Performance Order Storage (HPOS) compatible
WooCommerce Checkout Blocks compatible
Transaction details visible in the order admin panel
Debug logs integrated with WooCommerce

Requirements:

WordPress 5.8+
WooCommerce 6.0+
PHP 8.0+
Active TAFI merchant account, available at the TAFI merchant portal

Automatic installation (recommended):

In your WordPress dashboard go to Plugins > Add New
Search for "TAFI Pay"
Click "Install Now" and then "Activate"

Manual installation:

Download the plugin ZIP file
Go to Plugins > Add New > Upload Plugin
Upload the ZIP and activate the plugin

Configuration:

Go to WooCommerce > Settings > Payments
Click on "TAFI" to configure it
Enter your API Key and Merchant ID (obtained from the TAFI merchant portal)
Copy the displayed Webhook URL and register it in your TAFI panel
Choose the environment (Sandbox for testing, Production for live sales)
Save changes

1.1.5

The checkout now reads "Pagar con" followed by the TAFI logotype, instead of "Pagar con TAFI" printed beside a logotype that also spells the name. Stores still on the previous default are migrated automatically; a merchant who typed their own title keeps it.
The logotype ships as SVG instead of PNG. The old file was 80x52 with the artwork occupying 51x24 in the middle, so 54% of its height was transparent padding and every height the stylesheet asked for lost more than half of it to empty space: it rendered about 13px tall beside card logos roughly three times that. The SVG has no padding and stays sharp on any display density.
The logotype is now the dark variant. The previous pink-on-white artwork measured 2.34:1 against a white checkout where a card brand such as Visa measures 14.2:1, so it read as faint as well as small.
Added a "Logotipo" setting so stores whose checkout sits on a dark background can switch to the white logotype. It is a setting rather than an automatic prefers-color-scheme swap because that media query reports the visitor's operating system theme, not the merchant's checkout background — keying off it would paint the white logotype onto the usual white checkout.
The gateway icon rule is now scoped to TAFI. It was #payment ul.payment_methods li img, which sized every gateway's icon on the checkout page rather than only ours. On stores where that rule was taking effect, other payment methods' logos return to the size their theme intends.
The classic checkout and the Blocks checkout now take the logotype height from one number. They had drifted apart to 28px and 24px respectively.
Orders, emails and My Account still record "TAFI" as the payment method even though the visible label no longer spells it, and the logotype's alt text now says "TAFI" instead of repeating the gateway title.

1.1.4

Narrowed the pending-order guard so it can no longer reach code paths it was never meant to touch. WooCommerce applies the same filter inside WC_Order::status_transition() to decide whether a transition counts as payment received, so on 1.1.2 and 1.1.3 the hook woocommerce_order_payment_status_changed stopped firing for TAFI orders when they were finally paid, which could leave analytics, ERP or accounting integrations without the event. Nothing in WooCommerce core listens to it, so stores without such integrations were unaffected. The guard now applies only while the order is still pending.

1.1.3

Fixed a critical regression introduced in 1.1.2: TAFI orders were marked as paid at checkout without any credit request being sent. The 1.1.2 guard removed "pending" from the statuses WooCommerce considers payable, but both checkouts decide whether to call the payment gateway at all by asking needs_payment() on the order that was just created — which is pending — so they skipped the gateway entirely and ran payment_complete() instead. No WhatsApp request was sent and the order went straight to the confirmed state. The guard now engages only once a credit request actually exists on the order, which is the window it was meant to protect. Update immediately if you are on 1.1.2.

1.1.2

Added a "Cancelar y elegir otro método de pago" button to the confirmation page. It annuls the credit at TAFI, moves the order to "failed" and sends the customer to the order's payment page, where every gateway the merchant offers is listed — including TAFI itself, which starts a fresh credit request on the same order. No second order is created. If the customer happens to sign in WhatsApp while deciding, the credit is checked first and the cancellation is refused rather than releasing a paid order for payment again.
Fixed the sandbox availability check hiding TAFI on the order payment page: it measured the cart, which is empty by then, so a customer retrying with TAFI never saw it offered.
Fixed two retry bugs on orders that get a second credit request: the status-check counter was not reset, so the first scheduled check could immediately auto-cancel the new request, and a leftover scheduled check from the previous request was left in the queue.
Fixed a double-payment risk on the order confirmation page: while the 5-minute WhatsApp countdown was running, WooCommerce still offered its native "Pagar" and "Cancelar" order actions, so a customer could pay the same order again with another gateway or cancel it locally while the credit stayed open at TAFI. Both actions are now blocked for pending TAFI orders, at the URL level and not just visually. "Failed" orders remain payable so customers can retry with another method after a rejection.
When a credit is never signed, the order is now annulled at TAFI (step 7, anularsolicitudcredito) before being cancelled locally, on both the browser timeout path and the scheduled-check fallback. Previously the order closed in WooCommerce while TAFI kept holding the request until it expired on its own.
The phone field at checkout now explains that customers who are not TAFI users yet can sign up from WhatsApp in minutes, with a "Registrarse" link to TAFI's onboarding line. Filterable via tafi_register_whatsapp_url.
Admin styles and the order-screen script no longer load while editing unrelated post types.

1.1.1

Fixed a critical error that broke the block editor: when the gateway was set to the sandbox environment, opening or creating any post or page returned "There has been a critical error on this website". WooCommerce asks every gateway whether it is available while loading editor assets, and the sandbox amount check dereferenced the cart, which does not exist outside the frontend.
Tested with WordPress 7.1

1.1.0

Thank-you confirmation block now renders above the order summary so the customer sees the WhatsApp flow first
New modal pop-up that announces the final state (approved, rejected, expired) on top of the page
Fixed reconciliation bug: status checks now mark the order as paid as soon as the customer signs in WhatsApp (estadoCredito "Aceptado" with creditoFirmado true), matching the webhook behaviour
Added a "Consultar estado en TAFI" button in the order admin screen so merchants can manually trigger an API check when the customer's tab closed before polling resolved
Manual status-check action is now available on any TAFI order, not only those still pending
Background safety-net: when an admin loads the dashboard, the plugin sweeps TAFI orders stuck in "pending" for 5+ minutes and reconciles them against the TAFI API. Throttled to one sweep every two minutes. Runs independently of wp-cron so it works even on sites where scheduled tasks are unreliable.

1.0.0

Initial release
Full integration with the TAFI API
Webhook confirmation support
HPOS compatibility
Settings panel
Debug logging

TAFI - Págalo Relax

标签

下载

详情介绍:

安装:

升级注意事项:

常见问题:

更新日志: