Flagship vertical
Peptides & research products
Payment infrastructure for peptide and research-product businesses, built around underwriting rather than around a single processor.
Protecting revenue
Chargeback protection
Chargebacks cannot be eliminated. They can be seen earlier, answered properly and kept from reaching the ratio that costs a merchant their account.
No provider can prevent chargebacks. These tools reduce and manage them.
The basics
What a chargeback actually is
A chargeback is not a refund. A refund is something a merchant chooses to do. A chargeback is a cardholder going to their bank instead of to you, and the bank reversing the payment on their behalf - often before anybody has asked you what happened.
That difference matters because of what follows. A refund costs you the sale. A chargeback costs you the sale, the goods, a fee, and a mark against a ratio that your acquirer is watching. Enough of them and the question stops being about the money and starts being about whether you keep the merchant account at all.
Why the ratio is the real risk
Card networks and acquirers monitor chargebacks as a proportion of transactions, measured monthly. Cross the threshold and a merchant enters a monitoring programme: more scrutiny, higher fees, mandatory remediation, and - if it does not improve - termination.
The ratio is also where merchants get caught out by success. Volume falls in a quiet month while disputes from a busy month land, and a business with an unchanged number of chargebacks watches its percentage climb for reasons that have nothing to do with what it did.
Who is involved
Four parties, and only one of them is you. The **cardholder** raises the dispute. Their **issuing bank** decides whether to pass it on. The **card network** sets the rules and the reason codes. Your **acquirer** takes the money back from you and passes the case along.
The merchant is the last to find out and the first to lose the money. Everything useful you can do happens either well before the dispute or in a narrow window after it.
Common causes
Where chargebacks actually come from
Most merchants assume fraud. Most chargebacks are not fraud.
-
Unrecognised descriptor
The name on the statement is not the name on the website. The cardholder does not recognise the charge, assumes fraud, and calls the bank. Entirely preventable and remarkably common.
-
Delivery and fulfilment
Goods arrived late, arrived damaged, or the tracking says delivered and the customer says otherwise. A dispute about logistics that arrives as a dispute about payment.
-
Subscriptions and renewals
A recurring charge the customer forgot about, could not find how to cancel, or thought they had already cancelled. The single largest source of disputes in subscription businesses.
-
Product not as described
What arrived does not match the page that sold it. Often a photography or specification problem rather than a deliberate one.
-
Friendly fraud
The cardholder made the purchase, received it, and disputed it anyway - sometimes as a shortcut around a returns process, sometimes deliberately.
-
True fraud
The card was genuinely used by somebody who was not entitled to it. The one category where the cardholder is a victim too.
Reason codes vary by card network and change over time. What follows describes the underlying causes rather than any particular code set.
Two very different problems
Friendly fraud and true fraud need opposite responses
They arrive looking identical - a dispute, a reason code, money gone - and almost every merchant treats them the same way. That is why so much effort produces so little.
Friendly fraud
The cardholder made the purchase. They received what they ordered. They disputed it anyway.
Sometimes it is deliberate. More often it is a shortcut: the returns process looked slow, the cancellation link was hard to find, a family member used the card, or six weeks passed and the statement line no longer meant anything to them.
Friendly fraud is fought with **evidence and friction removal**. Evidence, because you can demonstrate the customer received exactly what they bought. Friction removal, because a customer who can cancel or return easily does not need their bank to do it for them.
True fraud
The card was used by somebody not entitled to use it. The cardholder is a victim, the transaction should not have happened, and no amount of delivery evidence helps - proving the goods arrived proves they arrived at the fraudster.
True fraud is fought **before authorisation**, not after the dispute. Screening, verification, velocity limits and authentication. By the time it is a chargeback the decision that mattered was made weeks ago.
Why telling them apart is the whole job
Fighting true fraud with evidence wastes time on cases that cannot be won. Fighting friendly fraud with tighter screening declines good customers to prevent disputes that screening was never going to catch.
Knowing which one you have is the difference between a programme that works and one that just costs money.
The dispute lifecycle
What happens, and where you can act
Deadlines are set by the card networks and are short. Missing one loses the case regardless of the merits.
-
Before the dispute
Screening, a recognisable descriptor, working cancellation and returns, and records kept. Almost all of the available leverage is here.
-
The alert window
Where the network and issuer support it, some disputes surface as an alert first. Refunding at this point stops it becoming a chargeback and counting against the ratio.
-
Chargeback raised
The issuer reverses the payment and assigns a reason code. The money is already gone; the code tells you what case you have to answer.
-
Representment
The merchant submits evidence for the specific reason code, inside the deadline. Generic evidence is why most representments fail.
-
Decision, then arbitration
The issuer decides. Escalation exists but carries fees that frequently exceed the transaction, so it is a commercial decision, not a point of principle.
Exact stages, names and time limits vary by card network and change over time. Apex confirms the ones that apply to your specific arrangement rather than publishing a set that may not.
Evidence
What a representment actually needs
A reviewer has minutes, not hours, and is answering one narrow question. Everything that does not answer it is noise.
-
Proof of delivery
Tracking with a delivery confirmation, the address it was sent to, and where available a signature.
-
Proof of the transaction
IP address, device, timestamps, and the AVS and CVV results at authorisation.
-
Proof of use
Logins, downloads, redemptions or service usage after the purchase - particularly powerful for digital goods.
-
Proof of agreement
The terms accepted, the cancellation policy shown, and the checkbox or click that accepted them.
-
The communication record
Emails, chat and support tickets - especially anything showing you offered a resolution first.
-
Purchase history
Previous undisputed orders on the same card, which is among the strongest arguments against a friendly-fraud claim.
Requirements differ by reason code. Compelling evidence for "goods not received" is irrelevant to "product not as described", and submitting the wrong set is the most common avoidable loss.
Prevention
The operational changes that move the ratio
Dispute tooling is the last line, and merchants reach for it first. The changes that actually reduce chargebacks are usually unglamorous and sit in the business rather than in the payment stack.
The descriptor
Make the statement descriptor match the name the customer bought from, and add a phone number if the format allows it. A meaningful proportion of disputes are cardholders who genuinely did not recognise a charge - and every one of those is a customer who would have called you instead if they could work out who you were.
Cancellation and returns
If cancelling is harder than disputing, customers will dispute. That is not a moral failing on their part; it is a rational response to the options you gave them. Make cancellation self-service, confirm it in writing, and send a renewal notice before charging.
Delivery expectations
Publish realistic timeframes and communicate when they slip. Most delivery disputes are raised in the gap between when a customer expected something and when they were told it would actually arrive.
Refund before it escalates
A refund costs the sale. A chargeback costs the sale, the fee and the ratio. On a marginal case the arithmetic usually favours refunding, and merchants resist it for reasons that are understandable and expensive.
Read your own data
Disputes cluster - one product, one shipping route, one traffic source, one subscription plan. A merchant who reviews reason codes monthly finds the cluster; one who reviews them after a warning letter finds it too late.
Revenue protection
What is actually at stake
The disputed amount is the smallest part of what a chargeback costs.
-
The transaction and the goods
The payment is reversed and, in a physical-goods business, the stock has already gone. Both sides of the sale are lost, not one.
-
The fee, every time
A chargeback fee is charged per case and is not returned when a merchant wins. Fighting a small transaction can cost more than conceding it, which is a commercial calculation worth making deliberately.
-
The monitoring threshold
Cross it and the account enters a remediation programme: higher fees, more scrutiny, and a timetable to fix it. The cost stops being per-transaction and becomes structural.
-
The account itself
A ratio that does not come back down ends in termination, and a terminated account makes the next one harder to obtain. This is the real risk, and it is the one merchants notice last.
What Apex does
Where Apex helps, and where it cannot
No provider can prevent chargebacks, and Apex does not claim to. What can be changed is how many become disputes, and how many disputes are answered properly.
-
Ratio monitoring
The ratio watched as operational data across the account, so a trend is visible while there is still time to act on it.
-
Alerts where supported
Where the network and issuer support it, disputes surfaced as alerts so they can be resolved before they count.
-
Evidence structured by reason code
Representments built to answer the specific question asked, submitted inside the deadline.
-
Reason-code analysis
Where disputes cluster, and what in the business is producing them.
-
Merchant education
Your team taught what each code means and what it needs, because they are closer to the evidence than we are.
-
Account structure
Where a profile allows it, arrangements built so one processor withdrawing is not the end of taking payment.
Alerting availability depends on the card network, the issuer and the processing arrangement. Apex confirms what is actually available on your account rather than describing a service in general terms.
How it works
What happens after you get in touch
-
Tell us about your business
What you sell, how you sell it, and what your current payment arrangement looks like.
-
We review your requirements
Your industry, ticket size, refund and dispute history and processing volume.
-
Suitable options are evaluated
The payment paths that fit your profile, with the trade-offs of each set out plainly.
-
Integration and onboarding
Account setup, gateway configuration and hardware, done alongside you.
-
Ongoing support
Monitoring, dispute handling and account reviews, with a route to a person.
Apex does not guarantee approval, a rate, a saving or a timeline. Underwriting decisions are made by the acquiring institution, and Apex's work is to put the strongest accurate case in front of it.
Who this helps
The businesses this is usually for
Availability depends on underwriting, and every merchant is reviewed individually.
E-commerce
Online retail on an established platform or a custom build, with checkout tuned for conversion and disputes kept in check.
Specialised vertical
CBD & hemp
Card and bank-based acceptance for CBD and hemp merchants, with the compliance documentation prepared before submission.
Specialised vertical
Nutraceuticals & supplements
Supplement merchants with recurring orders, where descriptor clarity and dispute handling decide whether an account survives.
Deferred delivery
Travel
Bookings taken well before delivery, which is what makes travel an underwriting conversation rather than a form.
Specialised vertical
Adult businesses
Adult merchants needing stable acceptance, clear descriptors and dispute handling that keeps ratios down.
Specialised vertical
Forex & trading
Trading platforms and brokerages, where deposit flow and dispute exposure are the underwriting question.
Specialised vertical
Tech support services
Remote support and software services, a category card networks watch closely.
Questions
Frequently asked
Does Apex only work with high-risk businesses?
No. Most Apex merchants are conventional businesses - shops, restaurants, professional firms, e-commerce stores - underwritten and priced as exactly that. Apex also handles specialised and complex verticals, which is where the deeper capability shows, but a traditional business is not placed on specialised terms because of who else we work with.
How is pricing decided?
Pricing follows underwriting. Card mix, average ticket, refund and chargeback history, the industry and how you take payment all feed into it. Apex does not quote a rate before seeing those, and does not guarantee a rate or a saving in advance.
Can Apex guarantee my account will be approved?
No, and no payment provider can. Approval is an underwriting decision. What Apex does is prepare the file properly before it is submitted - the website, the policies, the documentation and the processing history - which is what usually decides the outcome.
What happens if my current processor drops my account?
That is a common reason merchants come to Apex. Where the profile allows it, accounts are set up with more than one processing path from the start, so a single withdrawal does not stop revenue while a replacement is arranged.
Can I take card, bank and crypto payments together?
Yes, where the business qualifies for each. Card, ACH, eCheck and digital-asset settlement can run alongside one another under the same merchant relationship, with the gateway routing between them. What is available depends on the business type and underwriting.
Will Apex work with my existing website and systems?
Usually. Apex integrates with established storefront platforms, billing systems and CRMs, and does direct API work where an off-the-shelf plugin does not fit. Replacing a working system is rarely the right recommendation.
Related reading
Worth reading before you decide
Guide
Merchant accounts
What underwriting actually looks at
The parts of an application that decide the outcome, and the ones merchants spend time on that make no difference at all.
7 min read
Payment education
Payment education
How to read a processing statement
Interchange, assessments and markup, separated - so you can see which part of your rate is negotiable and which part never was.
6 min read
Guide
Risk and disputes
Keeping chargeback ratios down
Descriptors, refund policy, delivery evidence and alert handling: the four things that move the ratio, in the order they are worth fixing.
8 min read
Get started
Talk through chargeback protection
Tell us how your business takes payment and we will review whether this is the right arrangement for it.
- One conversation Underwriting, integration and support are handled by the same team.
- More than one path Where the profile allows it, accounts are set up with a fallback.
- Nothing overstated No promise of approval, a rate or a timeline before underwriting has looked at your business.
No obligation, and no application submitted without your agreement.
Get in touch
Questions about payments, an existing account, or anything else.