Beskrivelse
Outfalak Checkout replaces the cart-then-checkout journey with a single screen. A Buy Now
button beside Add to cart takes the shopper straight to one page that asks for a phone
number, a name, a PIN code and an address, and then charges the card.
The flow
Buy Now → phone (→ optional OTP) → name → PIN code, which fills in city and
state → address → payment method → pay → a real WooCommerce order.
Built on what your store already has
This plugin owns the checkout screen and nothing else. Products, prices, stock, tax,
shipping zones, coupons, orders, emails, invoices, reports and refunds all stay with
WooCommerce, already configured and already tested against your own couriers. Every
purchase creates a real WooCommerce order with real line items, so every report, every
export and every plugin that reads your orders keeps working.
What it adds
- One page, mobile first. No cart step, no account, no theme header to wander back out through.
- Buy Now on the product page. It is a second submit button inside WooCommerce’s own add-to-cart form, so the quantity, the variation and whatever a third-party plugin added all arrive with the click — without this plugin reimplementing a variation picker.
- PIN code autofill. Six digits fill in City and State. No API key, no setup.
- OTP on the phone number, when you connect a Outfalak account. Off otherwise.
- Saved addresses for returning shoppers, released only to a browser that has verified an OTP or placed an order with that number — never to anyone who merely types the number in.
- UPI, cards, net banking and Cash on Delivery through Razorpay, Cashfree or PayU.
- A COD fee and a prepaid discount, each with its own ceiling.
- A delivery estimate built from your dispatch cut-off, processing days, ship days and holidays.
- Abandoned checkouts, listed with the phone number as a WhatsApp link. Asking for the phone first means an abandoned checkout still leaves someone you can talk to.
- Branding — your store name, logo, colours and corner radius, inlined into the page head so they apply on the first paint.
How the money is kept safe
Prices are never taken from the browser. A Buy Now click carries a product id, a quantity
and the chosen options; every price is resolved from your catalogue and every total is
re-derived server-side immediately before charging.
Duplicate payments are blocked three ways: a per-attempt idempotency key reserved under a
unique index, the gateway’s own unique order reference, and a settlement table keyed by
order id, so whichever of the browser callback, the webhook and the UPI poll arrives first
wins and the rest stop.
A signed success callback is still verified server-side against the gateway, and the
captured amount is compared with the order total before anything is marked paid. Webhooks
are authenticated by signature alone — an unsigned request gets a bare 401 and changes
nothing.
Refunds
Refunds go through WooCommerce’s own order screen. The plugin registers a payment gateway
record — never shown at WooCommerce’s own checkout — so that the refund button on
these orders is the real one, and money actually goes back.
Speed
The checkout ships about 40 KB of JavaScript, one stylesheet and one self-hosted font, all
from your own origin. No framework, no font CDN, no third-party script your blog installed.
It renders as a standalone document rather than a theme template, so a CSS collision cannot
land on the pay button.
Developers
outfalakcheckout_order_settled— fires once per order, immediately after it settles.outfalakcheckout_settings— filters the resolved settings map.outfalakcheckout_view_data— filters the data a template renders.outfalakcheckout_api_base— filters the host the Outfalak platform is reached at.
A theme can take the checkout over entirely by dropping
outfalak-checkout-for-woocommerce/checkout.php into its own directory.
High-Performance Order Storage and the cart/checkout blocks are both declared compatible;
orders are read and written only through WooCommerce’s CRUD API.
External services
This plugin talks to outside services. Which ones depends on what you switch on — with
a fresh install and no credentials entered, only the PIN-code lookup below is ever used.
1. India Post PIN code directory — api.postalpincode.in
Used to turn a six-digit PIN code into a city and state while the shopper is filling in the
address. The PIN code alone is sent. Nothing identifies the shopper, the order or your
store. Results are cached, so a PIN already looked up is not sent again. If the service is
unreachable the plugin falls back to an offline prefix map and then to plain typing. This
runs without any configuration.
Website policies, including terms of use and privacy: https://www.indiapost.gov.in/website-policy
2. Razorpay — api.razorpay.com, and checkout.razorpay.com in the shopper’s browser
Used only when you enter Razorpay credentials and make Razorpay the active gateway. To
create the payment, verify it, read its status and issue refunds, the plugin sends the order
amount and currency, your order number, and the shopper’s name, email address and phone
number. The browser additionally loads Razorpay’s own checkout script to display the payment
sheet.
Terms of use: https://razorpay.com/terms/
Privacy policy: https://razorpay.com/privacy/
3. Cashfree Payments — api.cashfree.com, sandbox.cashfree.com, and sdk.cashfree.com in the shopper’s browser
Used only when you enter Cashfree credentials and make Cashfree the active gateway. The
plugin sends the order amount and currency, your order number, and the shopper’s name, email
address and phone number, and reads the payment’s status back. The browser additionally
loads Cashfree’s own SDK to display the payment sheet.
Terms of use: https://www.cashfree.com/tnc/
Privacy policy: https://www.cashfree.com/privacypolicy/
4. PayU India — secure.payu.in, info.payu.in, and their test.payu.in sandbox
Used only when you enter PayU credentials and make PayU the active gateway. The shopper’s
browser is form-POSTed to PayU with the order amount, your transaction id, a product
description, and the shopper’s first name, email address and phone number; the plugin then
verifies the result server-to-server.
Terms of use: https://payu.in/online-pa-tncs
Privacy policy: https://payu.in/privacy-policy
5. Outfalak platform — outfalakcheckout.com
Optional, and used only after you connect a Outfalak account under WooCommerce → Outfalak
Checkout → WhatsApp. It delivers WhatsApp messages — OTP codes, order placed,
order confirmed and abandoned-checkout reminders — from Outfalak’s own WhatsApp Business
number, billed to your wallet there. Connecting sends your site URL and site name. Sending a
message sends the recipient’s phone number and the values that message needs, such as the OTP
code or the order number. An hourly request pulls your account settings and wallet balance
back.
Until you connect an account nothing is sent to this service, and OTP codes and notifications
are written to WooCommerce → Status → Logs instead.
Terms of use: https://outfalakcheckout.com/legal/terms
Privacy policy: https://outfalakcheckout.com/legal/privacy
Installation
- Install and activate WooCommerce first. This plugin will not run without it.
- Upload the plugin through Plugins → Add New → Upload Plugin, or install it from the plugin directory, and activate it.
- Go to WooCommerce → Outfalak Checkout and enter your payment gateway credentials. Each gateway has its own Save & test button, and the test makes a real authenticated call.
- Open any product on the storefront. Buy Now now sits beside Add to cart.
You can skip step 3 while you are trying it out. With no credentials entered, the checkout
opens a simulated payment sheet on a development site, so the whole funnel — including
the failure path — can be walked before any paperwork is done.
FAQ
-
Does it replace the WooCommerce checkout page?
-
No. WooCommerce’s own cart and checkout stay exactly where they are and keep working. This
plugin adds a second, faster route from the product page. Shoppers who use the cart are
unaffected. -
Are the orders real WooCommerce orders?
-
Yes — a real order with real line items, created through WooCommerce’s own API. Your
emails, invoices, reports, exports, packing-slip plugins and refunds all read the same object
they always did. -
Which payment gateways are supported?
-
Razorpay, Cashfree and PayU for online payments, plus Cash on Delivery. One online gateway is
active at a time; credentials for the others stay saved, so switching back is instant. -
Do I need a Outfalak account?
-
No. The checkout, PIN-code autofill, saved addresses, payments, COD, the delivery estimate
and the abandoned-checkout list all work without one. A Outfalak account is needed only to send
WhatsApp messages — OTP codes and order notifications. Without one, those are written to
the WooCommerce log instead. -
Can a shopper look up someone else’s address by typing their phone number?
-
No. Saved details are released only to a browser that has verified an OTP for that number or
has placed an order with it. Typing a number is not proof, and the endpoint that records a
number is never the one that grants trust. -
Where do shipping rates come from?
-
From WooCommerce, under WooCommerce → Settings → Shipping → Zones. The
plugin does not keep a second set. -
Does it work with High-Performance Order Storage?
-
Yes. Compatibility is declared and orders are read and written only through WooCommerce’s
CRUD API, so both storage engines work. -
What happens on a site with plain permalinks?
-
Every one of the plugin’s URLs falls back to its query-string form automatically, so a webhook
URL already saved in a gateway dashboard keeps working. -
Can my theme restyle the checkout?
-
It can replace it. Drop
outfalak-checkout-for-woocommerce/checkout.phpinto your theme
directory and that template is used instead.
Anmeldelser
Der er ingen anmeldelser for denne widget.
Bidragsydere & udviklere
“Outfalak Checkout for WooCommerce” er open source-software. Følgende personer har bidraget til dette plugin.
BidragsydereOversæt “Outfalak Checkout for WooCommerce” til dit eget sprog.
Interesseret i udvikling?
Gennemse koden, tjek SVN repository, eller abonner på udviklerloggen via RSS.
Ændringslog
2.3.0
- Updates for this build come from the WordPress.org plugin directory.
- Countdown and Frequently Bought Together are on by default now.
- Platform download email removed — WooCommerce mail is the only automatic copy, with a manual Send backup on the Orders screen.
- Download buttons no longer appear for files WooCommerce cannot serve; the product id is logged instead.
2.2.0
- Updates for this build come from the WordPress.org plugin directory.
- Countdown is now a simple evergreen minutes timer (MM:SS, centered, restart on every end) with a homepage bar, a shortcode, and ticker scripts that block themes cannot break.
- New: “Outfalak for every checkout” (on by default) sends cart, mini-cart and checkout links through the fast checkout.
- Buy Now spacing is now per-side pixels with a theme fallback per side.
- Orders screen shows the download-email status with a manual Send; the resend is dedupe-safe.
- Download button on the confirmation page opens in a new tab.
2.1.0
- Updates for this build come from the WordPress.org plugin directory.
- New: Countdown and Frequently Bought Together are now their own menu pages under Outfalak Checkout, instead of living inside Settings. The countdown banner shows on the product page and the checkout until the sale end date passes; the bundle box builds from upsells, cross-sells and related products and buys them all through the fast checkout in one go.
2.0.3
- Updates for this build come from the WordPress.org plugin directory.
- The mobile-verification switch is gone from the settings screen. Verification now runs wherever this site is connected and stays inert where it is not, so there is nothing to switch. Saving the notifications tab no longer risks turning it off.
2.0.2
- Updates for this build come from the WordPress.org plugin directory.
- The Orders screen now shows the commission recorded on each order.
- Platform commission is set per store, under Payments — a percentage of the order total, never added to what the shopper pays.
- Connecting to Outfalak now goes to the API host that issues the key, so a store key is accepted instead of reported as invalid.
2.0.1
- Updates for this build come from the WordPress.org plugin directory.
- The checkout and confirmation headers now always show the Outfalak Checkout logo.
- Digital carts no longer show a shipping line — not even a free one.
- Settings masthead and plugin icon updated to the new branding.
2.0.0
- Updates for this build come from the WordPress.org plugin directory.
- New: an Orders screen beside Abandoned checkouts, listing every order placed through this checkout with a link to its WooCommerce order.
1.6.20
- Updates for this build come from the WordPress.org plugin directory.
- The account panel at the top of the settings screen is one compact bar now: status, store, last sync, and three smaller actions.
1.6.19
- Updates for this build come from the WordPress.org plugin directory.
- New: an “Open dashboard” button beside Sync now. It opens your Outfalak Checkout account already signed in – the store key this site is connected with is the proof, so there is nothing to type.
1.6.18
- Updates for this build come from the WordPress.org plugin directory.
- A cart with only downloadable products now asks for one thing: an email address. No name box, no PIN code, no address. The email is checked as they type, and an empty box and a mistyped address are told apart.
1.6.17
- Updates for this build come from the WordPress.org plugin directory.
- Every switch on the settings screen is redrawn: a 40×24 track with the knob at top 5px / left 6px, travelling to the far end and taking the brand colour when it is on.
1.6.16
- Updates for this build come from the WordPress.org plugin directory.
- The Buy Now button now matches your theme. Leave its colours blank and it copies the background and text colour off WooCommerce’s own add-to-cart button on that theme, so a hex, a gradient or an oklch() the browser resolves is picked up as-is.
- Every colour field on the settings screen has a colour picker beside it now. Either one can be typed or picked; clearing the box is still how you go back to automatic.
1.6.15
- Updates for this build come from the WordPress.org plugin directory.
- The Buy Now button is a label again – the logo added to it in 1.6.14 has been removed.
1.6.14
- Updates for this build come from the WordPress.org plugin directory.
- The Buy Now button now carries the Outfalak Checkout logo, on the product page, in product listings, in the cart and in the shortcode.
1.6.13
- Updates for this build come from the WordPress.org plugin directory.
- On the Payments tab the active gateway’s keys now sit directly under the “Active gateway” picker instead of at the bottom of the tab, so the gateway you chose and its credentials are one block.
1.6.12
- Updates for this build come from the WordPress.org plugin directory.
- A cart with only downloadable products no longer asks for an address. The section becomes “Your download” and asks for a name and the email the download link goes to — the same email WooCommerce emails the link to, and the order-received page still offers the buttons.
- The settings screen now uses outfalakcheckout.com’s own colours, and the masthead shows the brand logo instead of a coloured square.
1.6.11
- Updates for this build come from the WordPress.org plugin directory.
- The Payments tab now opens only the selected gateway’s panel, with its own keys and test button. Pick a different gateway from the dropdown and its panel opens instead, before you save.
1.6.10
- Updates for this build come from the WordPress.org plugin directory.
- The wallet now sits at the top of the settings screen, above the tabs, instead of inside the WhatsApp tab — it is your account balance, so it is in view whichever section you are on.
- Updated the Outfalak Checkout logo shown in the checkout and order-received footer, and added the brand icon to the plugins list.
- The admin menu is now its own top-level item instead of sitting under WooCommerce. Its two screens (Settings, Abandoned checkouts) are unchanged, and the permission required is still the same.
1.6.9
- Updates for this build come from the WordPress.org plugin directory.
- Removed the Branding tab. Store name and logo are owned by your Outfalak Checkout account, so they are no longer editable on this screen; the checkout header falls back to your site title and site icon.
- Colours and Trust and support now live under Storefront, so every remaining setting is still reachable.
1.6.8
- Updates for this build come from the WordPress.org plugin directory.
- The wallet shown on the settings screen is now your Outfalak Checkout account balance — the same one you recharge from Account Wallet — and the line saying so is always visible, not only when the balance is low.
1.6.7
- Updates for this build come from the WordPress.org plugin directory.
- Mobile verification is on by default and applies itself once the site is connected — on a disconnected site it stays inert so no checkout is ever blocked over a code nobody can receive.
1.6.6
- Updates for this build come from the WordPress.org plugin directory.
- Settled orders now appear in the Outfalak dashboard under Orders — same order, same revenue, pushed the moment it settles.
1.6.5
- Updates for this build come from the WordPress.org plugin directory.
- The Buy Now button can now wear its own colours and hide WooCommerce’s Add to cart on product pages — all three live under Storefront.
1.6.4
- Updates for this build come from the WordPress.org plugin directory.
- Digital orders now show download buttons right on the confirmation page, reading the permissions the paid order grants — no waiting on the email.
- PayU UPI Seamless is on by default; it was already attempted before falling back to the redirect.
1.6.3
- Updates for this build come from the WordPress.org plugin directory.
- Connect now opens on the dashboard (
app.outfalakcheckout.com), where the approval screen lives — the old platform address only showed the dashboard home. - The “PayU UPI Seamless” toggle now saves and stays on; it previously reset on every save, so “Show QR” could never work on PayU.
- The store key exchange goes to the API host, so a fresh connect code is accepted instead of answered “already used or expired”.
1.6.2
- Updates for this build come from the WordPress.org plugin directory.
- Renamed the plugin, on both the display name and the slug, to Outfalak Checkout for WooCommerce (
outfalak-checkout-for-woocommerce), so its own listing name no longer reads as similar to another company’s checkout product, and so ownership of the listing is unambiguous. This plugin remains a client of the Outfalak Checkout platform, which is unaffected by this rename.
1.6.1
- Renamed the plugin, on both the display name and the slug, to Kuick Checkout for WooCommerce (
kuick-checkout-for-woocommerce), so its own listing name no longer reads as similar to another company’s checkout product. This plugin remains a client of the Outfalak Checkout platform, which is unaffected by this rename. - “Powered by Outfalak Checkout” on the customer-facing checkout is now off by default; a merchant switches it on rather than having it shown automatically.
- An icon helper’s extra HTML attributes are now escaped per attribute instead of concatenated as a raw string; every current caller already passed only fixed literals, so this changes nothing rendered, only how it is built.
1.6.0
- Renamed the plugin directory and entry file from
outfalak-checkout-for-woocommercetokuick-checkout-for-woocommerce. - A site already running an earlier version keeps its existing folder and file name through this update: the update checker renames the new release to match what is already installed, the same protection that carried the 1.1.x → 1.3.0 rename, now extended to also cover the entry file.
- A fresh install from this version on gets the new folder and file name; nothing about upgrading an old one forces a switch.
1.5.0
- Updates for this build come from the WordPress.org plugin directory.
- Two fields on the settings screen are now escaped where WordPress’s coding standard can see it. Both were already safe — only the annotation sat on the wrong line.
- Tested against WordPress 7.1 and WooCommerce 11.
1.4.1
- The Recharge wallet button on the Notifications tab reaches the wallet again. It still pointed at the old admin, which now redirects, so the button left merchants on a sign-in page instead of the top-up screen.
- Corrected the WordPress version this plugin is tested against. The header carried WooCommerce’s number, which is not a WordPress version at all.
1.4.0
- Updates come from outfalakcheckout.com again. 1.3.0 handed them to WordPress.org, where this plugin is not listed, which left an installed site with no way to hear about a fix.
- Updating from 1.1.x keeps the plugin’s existing folder name, so the site does not deactivate it mid-upgrade.
1.3.0
- Renamed to Outfalak Checkout for WooCommerce for the plugin directory listing.
- Updates now come from WordPress.org; the plugin’s own update checker has been removed.
- The Outfalak platform host moved from the Update URI header to the
OUTFALAK_API_BASEconstant and the newoutfalakcheckout_api_basefilter. - Removed an unused analytics script left over from an earlier port.
1.2.1
- Delivery estimate honours dispatch cut-off, processing days, ship days and holidays.
- Abandoned checkouts screen.
- Prepaid discount and COD fee, each with its own ceiling.
1.2.0
- Cashfree and PayU alongside Razorpay, with the UPI Seamless intent flow.
- Refunds from the WooCommerce order screen.
1.1.0
- Saved addresses for returning shoppers, gated on a verified OTP or a previous order.
- PIN code to city and state.
1.0.0
- First release.