Keep BigCommerce. Add WeRefund.

WeRefund reads your BigCommerce orders, the refunds recorded on them and your returns policy page, read‑only, and on a Stencil theme shows WeRefund Verified ✓ on the product page and in the cart.

Get started with BigCommerce Talk to Sales

$0 for the merchant; read-only access is set in your BigCommerce control panel when you connect your store.

Access: Read-onlystore_v2_orders_read_only store_v2_content_read_only on a store-level API account you create
Orders & refunds: Webhooksstore/order/created store/order/refund/created plus scheduled re-reads
Policy changes: Scheduled readsYour returns policy is a web page, captured for each order and read on a schedule
Badge: Product page & cartA script you add in Script Manager, no edits to your theme files (Stencil themes)

The connection

How the connection works

A store-level API account, created in your own control panel: you choose its permissions, you see its credentials once, and you can delete it at any time.

store_v2_orders_read_onlyOrders: read-only. Your orders, the products on them and the refunds recorded on those orders. The customer names, email addresses, phone numbers, billing and shipping addresses and any comment left at checkout are readable with it.

store_v2_content_read_onlyContent: read-only. Your web pages, blog posts, redirects and widgets. WeRefund lists your web pages so you can choose the one that holds your returns policy, then reads that page's content.

Webhooks default scopeAvailable to every API account without an extra permission. WeRefund registers its own subscriptions, and they are deleted with the account.

Every other scope stays at None, and read-only scopes allow only GET and HEAD requests. BigCommerce doesn't let you edit the scopes of an existing account: to change them, you delete it and create a new one.

01

Create a read-only API account

In your control panel, go to Settings › Store-level API accounts and click Create API Account. Choose the V2/V3 API token type, name it, and set Orders and Content to read-only. The store owner can do this, or a user the owner has given high-risk permissions.
02

Keep the credentials

When you save, BigCommerce shows the account's credentials in a pop-up, once, and your browser downloads them as a .txt file. The pop-up can't be shown again, so keep the file.
03

Paste them into WeRefund

You paste the access token and the API path into WeRefund, and WeRefund confirms that the account can read your orders and web pages. WeRefund then lists your web pages so you can choose the one that holds your returns policy. The token doesn't expire over time; to end WeRefund's access, you delete the API account.
04

First read, then stay current

Through BigCommerce's REST APIs, WeRefund reads the web page that holds your returns policy as it stands today — the version verification is based on — and your recent orders with the refunds recorded on them. It then registers its webhooks for new orders, order updates, refunds and page updates. From then on, webhooks signal new orders, updates and refunds and WeRefund reads them; the orders modified and the refunds created since the last read, and your policy page, are also read again on a schedule, which picks up a missed order or refund. Your policy page is captured again each time an order reaches WeRefund.

Data

What WeRefund reads, and how it stays current

Three things, read-only. Webhooks signal new orders and refunds; scheduled reads pick up policy page changes and the orders and refunds a webhook misses.

What WeRefund reads from BigCommerce, and how each item stays current
What WeRefund reads	From BigCommerce	How it stays current
Orders — line items, dates, status, and the customer details recorded on them	`/v2/orders` `/v2/orders/{id}/products` · Orders read-only	The `store/order/created` and `store/order/updated` webhooks, plus a scheduled read of the orders modified since the last one
Refunds recorded on those orders — amount, date, reason, payment	`/v3/orders/payment_actions/refunds` · Orders read-only	The `store/order/refund/created` webhook, plus a scheduled read of the refunds created since the last one
Your returns policy — a web page, as BigCommerce has no separate policy field	`/v3/content/pages` filtered on the page you chose, with `include=body` · Content read-only	Captured each time an order reaches WeRefund, and a scheduled read; a page update webhook, when BigCommerce sends one, can trigger an earlier read. BigCommerce's Pages API documents no last-modified date for a page, so its content is compared; a change is recorded as a new version and verified again, and a page set not to be visible isn't treated as your published policy

A BigCommerce webhook carries only IDs, not the order, refund or page itself, and can arrive twice. BigCommerce retries a failed delivery for up to 48 hours before switching the webhook off, and also switches off a subscription after 90 days without activity. WeRefund checks the secret header it registered with each webhook, ignores duplicates, checks that its subscriptions are still active, and reads recent orders and refunds again to catch what a delivery missed. On BigCommerce, a returns policy is a web page you create under Storefront › Web Pages (with Multi-Storefront, under that storefront in Channel Manager), so you confirm the policy page when you connect. Each time an order reaches WeRefund — when its store/order/created webhook is received, or when a scheduled read records an order a delivery missed — WeRefund captures your published policy page, on top of its regular scheduled check, and that order keeps the version captured for it. If your store takes payments through Stripe, PayPal, Adyen, Checkout.com or Airwallex, WeRefund also reads each order's payment and your refund events from that provider.

On your storefront

Where the badge appears

The WeRefund Verified ✓ badge is a script you add under Storefront › Script Manager (with Multi-Storefront, under that storefront in Channel Manager): Create a Script, placement Footer, location Storefront pages, with the script type, script and category WeRefund gives you when you set up the badge, then Save. Your theme files stay as they are. WeRefund could place the script itself only with a permission to modify content, so the connection stays read-only and you add it.

It shows no number: the exact terms stay in your policy, and each shopper sees the real deadline after the purchase.

Placement in a BigCommerce storefront

Product page Stencil themeShown

The script reads the page type Stencil provides and shows the badge on product pages. With BigCommerce's cookie consent banner on, a shopper who declines the script's category doesn't load it.

Cart Stencil themeShown

The same check, on the cart page, with the same cookie consent condition.

Blueprint themes LegacyNot shown

BigCommerce's legacy theme engine doesn't render Script Manager scripts.

Catalyst storefrontsDifferent set-up

Catalyst 1.1 and later run scripts without Handlebars (earlier versions don't run them), so this script can't read the page type; Catalyst stores need a different set-up.

CheckoutNot shown

You set the script's location to Storefront pages, which excludes checkout and order confirmation; don't choose All pages or Checkout.

What WeRefund never does

Hold your customers' payments

Shoppers pay through your checkout and your payment provider. WeRefund never holds your customers' payment funds.

Refund in your place

You refund as you do today, in your BigCommerce control panel or with your payment provider. WeRefund reads the refund recorded in BigCommerce or, if your store takes payments through Stripe, PayPal, Adyen, Checkout.com or Airwallex, sent by that provider; it never creates one.

Change your checkout pages

The badge lives on the product page and in the cart of a Stencil theme; nothing is added to checkout pages.

Write to your store data

With Orders and Content set to read-only, the API account you create can only read them; the only things WeRefund creates are its own webhook subscriptions.

Set up

Three steps on BigCommerce

01
Create your WeRefund account

$0 setup, $0 monthly fee, $0 processing surcharge.
02
Connect your store & payment provider

Choose BigCommerce, create a store-level API account with Orders and Content set to read-only, paste its access token and API path into WeRefund, and choose your returns policy page. If your store takes payments through Stripe, PayPal, Adyen, Checkout.com or Airwallex, connect that provider too.
03
Get Verified

WeRefund reads your returns policy page and verifies it. Once it passes, add the WeRefund script in Script Manager; on a Stencil theme the badge shows on your product page and in your cart.

Add the banner to your theme

Paste it once before the closing body tag: it reads your after-sales score from your WeRefund profile and turns itself off the day verification stops.

See the eight formats

4.7 / 5 · 1,284 return reviews See the profile →

<script src="https://js.werefund.com/badge.js" data-store="your-store" data-format="strip" async></script>

FAQs

BigCommerce questions

All integrations

Five payment providers and seven store platforms.

Integrations

WeRefund API

Endpoints, fields and examples, in preview.

API reference

?Does WeRefund change my BigCommerce theme?

No edits to your theme files. The badge is a script you add under Storefront › Script Manager, in the footer of Storefront pages, and you can delete it there at any time. It needs a Stencil theme: the legacy Blueprint engine doesn't render Script Manager scripts.

?What access does WeRefund ask for?

A store-level API account that you create, with Orders and Content set to read-only and every other scope at None. The store owner, or a user the owner has given high-risk permissions, creates it under Settings › Store-level API accounts. Its token doesn't expire over time. To end WeRefund's access, delete the API account, which also deletes WeRefund's webhooks. To remove the badge, delete the WeRefund script under Storefront › Script Manager. BigCommerce doesn't let you edit an existing account's scopes.

?How does WeRefund see a change to my return policy?

BigCommerce has no dedicated policy field: your returns policy is a web page, created under Storefront › Web Pages. WeRefund reads that page on a schedule and compares its content, since BigCommerce's Pages API documents no last-modified date for a page; a page update webhook, when BigCommerce sends one, can trigger an earlier read. A change is recorded as a new version and verified again; if it stops passing, verification becomes unavailable, and a page set not to be visible isn't treated as your published policy. WeRefund also captures your published policy page each time an order reaches it, so each order keeps the version captured for it.

?What if a webhook never arrives?

BigCommerce retries a failed delivery for up to 48 hours, then switches the webhook off; it also switches off a subscription after 90 days without activity, and a delivery can arrive twice. WeRefund checks the secret header on each webhook, ignores duplicates, checks that its subscriptions are still active, and reads the orders modified and the refunds created since its last read, so a missed order or refund is picked up on the next read.

?Can the badge appear at checkout?

?Does WeRefund issue refunds in BigCommerce?

No. You refund as you do today, from Orders › All orders in your BigCommerce control panel or in your payment provider's dashboard. A refund made in a provider's dashboard reaches WeRefund once you record it on the order in BigCommerce, or from the provider when it is Stripe, PayPal, Adyen, Checkout.com or Airwallex. WeRefund reads the refund recorded on the order in BigCommerce and, if your store takes payments through one of those five providers, the refund event from that provider, and records it against the order in WeRefund. Set to read-only, the API account can't create a refund, and WeRefund never holds your customers' payment funds.

More store platforms

Shopify

shopify.com

Reads your orders, the refunds recorded on them and your Refund policy from your Shopify store. The badge renders on the product page and in the cart, as a theme app block or app embed.

Store platforms

WooCommerce

woocommerce.com

Reads your orders through the WooCommerce REST API and webhooks, and your return policy page through the WordPress REST API. The badge renders on the product page and in the cart, where your theme's templates allow it.

Store platforms

Magento

magento.com

Reads your orders, their refunded totals and your return policy page from your Magento store. In Luma and themes that keep its layout containers, the badge renders on the product page and in the cart.

Store platforms

PrestaShop

prestashop.com

Reads your orders, credit slips and return policy page from your PrestaShop store. In themes that call its two display hooks, the badge renders on the product page and in the cart.

Store platforms

Wix

wix.com

Reads your orders, their refunds and the Return policy in your Wix checkout settings. The badge renders on the product page and, where your store uses it, in the side cart.

Store platforms

Custom / Headless

WeRefund API

For a custom or headless store, your orders reach WeRefund through the API, in preview.

Store platforms

Verification, not a migration

Keep your PSP. Add trust.

$0 setup. $0 monthly fee. $0 processing surcharge. Your store, your provider and your merchant account stay as they are.

Talk to Sales Get Verified

Keep BigCommerce. Add WeRefund.

How the connection works

Create a read-only API account

Keep the credentials

Paste them into WeRefund

First read, then stay current

What WeRefund reads, and how it stays current

Where the badge appears

What WeRefund never does

Hold your customers' payments

Refund in your place

Change your checkout pages

Write to your store data

Three steps on BigCommerce

Create your WeRefund account

Connect your store & payment provider

Get Verified

Add the banner to your theme

BigCommerce questions

More store platforms

Shopify

WooCommerce

Magento

PrestaShop

Wix

Custom / Headless

Keep your PSP. Add trust.