Refund Policy for High-Risk Merchants: Writing One Underwriters Accept

A refund policy that passes underwriting states what is refundable, within how many days, on what conditions, how to ask and how the money returns to the original card, shown before checkout and matched to the product. An underwriter reads it for dispute exposure; a dispute analyst reads it against one claim. A refund before a dispute costs the sale; a chargeback costs the sale, a fee and a ratio count. Counsel checks the consumer-law minimums.

A refund policy for a high-risk merchant is a short page in plain words that states what can be returned or cancelled, within how many days, on what conditions, how the customer asks, and how and when the money goes back to the card. It sits where the customer sees it before paying, describes the product actually sold, and is applied the same way on every order. An underwriter reads it at boarding to estimate disputes; a dispute analyst reads it months later against one customer's claim. Below: what each reader looks for, where the policy must appear, how to fit it to the product, and why a fast refund usually costs less than the chargeback it prevents.

Two readers: the underwriter and the dispute analyst

The underwriter opens your website during the KYB review and reads the refund policy next to the checkout page. The questions are practical: is the policy there, can a customer find it before paying, does it describe the product on the site, and does it imply a dispute rate the acquirer can carry at your MCC. The dispute analyst arrives months later with one transaction and one claim: the goods never arrived, the subscription was cancelled, the refund never posted. The analyst compares the claim with what your policy said on the day of the sale and whether you applied it. A clear policy, shown before checkout and followed to the letter, is evidence for you; a buried one, changed after the sale or ignored by your own support team, is evidence for the other side.

Where the policy must appear

The card networks typically require that refund and cancellation terms be disclosed to the cardholder before the sale is completed, and dispute reasons exist for a customer who was not told. So the policy is visible or linked on the checkout page itself, near the pay button, not only in the footer. The wording must be identical wherever it appears: a 30-day window on the policy page and a 14-day window in the confirmation email is an inconsistency the analyst holds against you. The checkout terms and policies checklist on this blog covers the other pages the acquirer expects next to it.

• Checkout page. A one-line summary next to the pay button, a link to the full policy, and the words the customer agrees to when ordering.
• Footer of every page. The full policy at its own URL, in the same wording as the checkout summary.
• Product page. Any exception for that product, such as a custom item or a digital download, stated where the customer decides.
• Confirmation email and receipt. The window, how to request a refund and the support channel, in writing.
• Support replies. Your team quotes the policy, never a looser or stricter version.

Match the policy to what you sell

A common way to fail underwriting is a policy copied from a template written for another product. A physical-goods policy on a coaching site promises returns of something that cannot be returned; a digital-download policy on a supplement store says nothing about opened bottles. The underwriter reads the mismatch as a merchant who has not thought about disputes; the dispute analyst reads it as a policy that does not cover the transaction.

The examples show the shape; the numbers are placeholders. Pick windows you can honour on every order, and have counsel confirm that they meet the consumer-law minimums of every market you sell into. Several markets give buyers a statutory right to cancel a distance sale, and a policy that offers less than the law is a finding against you at review and a lost argument in a dispute. IBOCore gives no legal or tax advice; a professional decides what your markets require.

The eight sections of a refund policy that passes review

1. Scope. The products and the brand covered, and the legal entity that issues the refund, so the policy, the billing descriptor and the merchant application carry the same name.
2. Window. How many days the customer has, counted from delivery for goods and from purchase for digital products and services.
3. Conditions. The state the goods must be in, the proof you ask for, and the exceptions by product type.
4. How to request. One staffed channel, an email address on the company domain or a form, and the response time to expect.
5. How and when the money goes back. Always to the original payment method, within a stated number of business days, with a note that the issuing bank may take longer to show it.
6. Partial refunds and store credit. When a partial refund applies, and that store credit is an option the customer can decline.
7. Cancellation for recurring billing. How to cancel, when it takes effect, what happens to the current period, and what a trial becomes.
8. Contact and entity details. The support email, the support phone if the descriptor carries one, and the legal name and address of the entity.

Refund timing and the refund-versus-chargeback trade-off

A refund and a chargeback both return the sale amount to the customer; the difference is everything else. A refund costs the sale and, on many pricing schedules, the processing fees of the original transaction. A chargeback costs the sale, a dispute fee billed whether you win or lose, a possible reserve debit, and one more dispute in the ratio your acquirer and the card networks monitor, the count that decides your reserve terms and, past the network thresholds, whether the MID survives. The chargeback fees guide on this blog prices each of those lines; this article stays on the policy.

So any complaint that could become a dispute is cheaper to refund than to argue, as long as the refund lands before the dispute is filed. Speed is the point: a customer who gets no reply calls the bank instead of waiting for one. Refund a request inside the policy the same business day, and give a request outside it a written decision the same day, even when the answer is no. The customer support guide on this blog covers the response times acquirers expect.

• Refund to the original card only. A refund to another card, a bank transfer or a wallet leaves the original transaction disputable and looks like refund fraud.
• Refund before the dispute posts, never after. Once a chargeback is filed, answer through the acquirer's dispute process; a refund on top credits the customer twice.
• Tell the customer the timing in writing. A customer who does not know when the credit will show can file a "credit not processed" dispute in the days between your refund and its appearance on the statement.
• Log every refund with its reason. The log proves the policy is applied as written.
• Use pre-dispute alerts where your acquirer offers them. Refunding a questioned transaction before it becomes a chargeback loses the sale but avoids the dispute fee and the network's dispute count; ask whether your acquirer counts alerts in its own ratio.

Refund policy on a fresh US entity

The policy is issued by the legal entity that holds the MID, so its scope section names that entity and the brand it trades under. On an IBOCore package the entity is a US LLC or C-Corp incorporated in the director's home state with its EIN issued, and the director is the IBO (Independent Business Operator), a real, KYC-verified US resident with a credit score of 650 or more who stays available for verification calls. The professional email on the company domain, included in the package, is the support address. The state filing and the EIN letter show that entity and its director; the policy, the billing descriptor and the merchant application carry the same entity name.

Two more points. The optional document template pack, $499 one-time, includes refund policy and terms of service templates you adapt to your product; they are a starting point, not legal advice. The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model. IBOCore does not manage refunds or disputes; the policy, the refunds and the ratio are yours.

Questions merchants ask

Can a high-risk merchant have a no-refund policy?

You can write one, and some products justify it: custom goods, digital files after download, services already delivered. Two limits apply. Consumer law in several markets gives buyers a right to cancel a distance sale that a policy cannot remove; counsel confirms which rules bind you. And a blanket no-refund clause does not stop disputes, it redirects them: a refused customer calls the bank, the chargeback lands with its fee and ratio count, and a policy the analyst judges hidden or unfair does not win the case. Refuse refunds only where the product makes the reason obvious.

How long should the refund window be?

Long enough that a customer with a genuine problem asks you instead of the bank, and short enough that you can still verify the claim. Count from delivery for goods and from purchase for digital products and services, and say which. A window that closes before the goods can arrive is a defect an underwriter notices. What matters more than the number is that it is the same on the checkout page, the policy page and the confirmation email. The statutory minimums of your markets set the floor; a professional confirms them.

Can I change the refund policy after the MID is approved?

Yes, with two rules. Each order is governed by the policy in force on the day of its sale, so keep a dated archive of every version with a screenshot of the checkout at each change; the dispute analyst reads the version the customer saw, not the current page, and a new version never applies to orders placed under the old one. And the terms the underwriter approved are the ones on file with the acquirer: a looser policy lowers your dispute exposure, while a tighter one, for example a shorter window or a new exclusion, raises it and is a change to tell the acquirer about before it goes live. Update the checkout summary, the policy page and the confirmation email together, so the three never disagree.

Compliance touchpoints that survive audit

Clean setups disclose beneficial ownership, file BOI, use genuine IDs, and keep the IBO informed of website and descriptor changes. Processors re-scan for prohibited products, undisclosed aggregation, and transaction laundering. Violations land on MATCH and kill future MID applications.

• AML / CDD: customer due diligence on the merchant entity.
• PEP screening: politically exposed persons get enhanced review.
• OFAC / SDN: sanctions lists checked on owners and signers.
• Website compliance: refund policy, terms, pricing visible before checkout.

Compliance shortcuts that trigger MATCH

Fake guarantors, borrowed SSNs, cloaked websites, and third-party processing through your MID are the fastest paths to MATCH listings. Recovery requires legal work and years of delay. Disclose, document, and keep the IBO in the loop.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.