The complete module page

Antifraud & Chargeback: fewer losses without turning away real graduates

A risk score explained by signals on every paid ticket, store order, gallery product, album and event consumption purchase. Release rules by sale type and payment method, a review queue with deadlines, duplicate detection, block and trust lists, chargeback tracking fed automatically by Asaas, Stripe and Mercado Pago, a versioned PDF evidence package, a risk list at the event entrance, billing disputes opened by graduates in the app and a report of losses avoided. Money is never held: what waits for review is the delivery.

This is the whole module reference on one page: the eight admin screens, the sixteen score signals, the rules that come ready, each functional area with every feature listed, the design decisions that explain why the system releases when in doubt, the boundaries with other modules and a glossary of fraud and dispute terms.

Talk to a specialistSee plans
  • 16risk signals in the score, each with the sentence that explains why it fired
  • 5protected sale types: tickets, store, gallery products, albums and consumption
  • 3gateways with automatic chargebacks: Asaas, Stripe and Mercado Pago
  • 8admin screens, from the simulation dashboard to the losses avoided report
  • 0money held: what waits for review is the delivery, never the payment

Inside the module

10 screens, in the order the work happens

Four blocks in the admin menu. Review decides what is delivered right away and what waits for someone to look, disputes handle what already became a card chargeback, the graduate and the entrance are the two ends that see the module outside the office, and configuration keeps only what the company changed in the rules that come ready.

01

Purchase review

The score of every paid sale, what was held and who decides.

4 screens
  • DashboardPurchases under review, overdue review deadlines, what was held (or would have been, in observation mode), decisions in the period with the share of legitimate graduates, the queue due first, the signals that fired most and the split by sale type.
  • Simulation with real salesRuns the engine now over the latest paid sales, with the current rules and without saving anything. Shows how many purchases would be held, which ones and why. Works from the first minute after subscribing.
  • Purchases under reviewThe queue of held sales, with score, reason, deadline and the detail of each signal. Approving releases delivery immediately; rejecting keeps it held and can block the CPF, email, card or IP for future purchases.
  • DuplicatesWhat is already in the database and deserves a look: the same card on several accounts, the same CPF on several records, the same mobile number, repeated ticket purchases, extra tickets issued and bills paid twice.
02

Disputes

The chargeback that came through the card, and the defense built from what the system already stores.

2 screens
  • ChargebacksOpen disputes with amount, reason, gateway, response deadline and owner. Notices from Asaas, Stripe and Mercado Pago arrive on their own; Rede, Cielo, Stone and other acquirers are recorded by picking the payment in a search, with no code to type.
  • Evidence packageInside the chargeback: what proof exists right now, section by section, and the PDF generated in versions that never overwrite each other, with the SHA-256 stored and the date it was sent to the acquirer.
03

Graduates and entrance

The two ends that see the module outside the office.

2 screens
  • Billing disputesThe queue of disputes opened by graduates in the app, with protocol, conversation, internal notes the graduate never sees, requests for a reply and a decision for the graduate or keeping the charge.
  • Entrance listPer event, the tickets that require an ID check at the door and the few that cannot enter, with the reason for each and a printable version.
04

Rules and leadership

What the company changed in the ready rules, and the number leadership follows.

2 screens
  • Rules & ListsObservation mode or holding on, a rule per sale type and payment method, risk bands, the weight of each signal, block and trust lists and the history of who changed what.
  • Losses avoidedMonth by month: sales reviewed, blocked, confirmed legitimate, disputes won and lost, billing disputes resolved before the bank, false positive rate and chargeback rate over card payments.

The problem and the fix

What changes day to day for finance, the entrance team and leadership

The pain

The chargeback shows up on the statement two months after the ball, when the ticket was already used and the photo already delivered.

With Partiu Formatura

The dispute notice from Asaas, Stripe and Mercado Pago becomes a case the same minute, with a response deadline, and the ticket from that purchase starts requiring an ID check at the entrance.

The pain

To avoid fraud, someone suggested holding every card payment for three days, and support filled up with graduates without tickets.

With Partiu Formatura

The score tells an ordinary purchase from a strange one. The default rule only holds high score card sales, pix and bank slips release right away, and a graduate with installments paid on time earns trust points.

The pain

Nobody can tell whether the antifraud rule is avoiding losses or just getting in the way of good customers.

With Partiu Formatura

The module starts in observation: it reviews everything, records what it would have held and holds nothing. The simulation with real sales and the false positive rate answer the question before holding is switched on.

The pain

The purchase was held, the reviewer went on vacation, and the graduate had no ticket the day before the event.

With Partiu Formatura

Every hold has a deadline. Tickets and consumption release on their own when the deadline passes without a decision; physical products stay held, because a shipped box does not come back.

The pain

To answer the acquirer, finance hunts for the contract, the acceptance, the receipt, the entrance scan and the tracking in five systems.

With Partiu Formatura

The evidence package gathers it in one PDF: the payment with IP and device, the account holder, contract acceptance with IP and hash, the ticket used at the entrance, delivery tracking and authorized conversations. What does not exist shows as missing.

The pain

The same card pays installments for three different graduates and nobody notices until the first chargeback.

With Partiu Formatura

The card is identified by BIN and last digits, never by the number. The duplicates screen shows where it circulates, and the card on several accounts signal weighs on the next purchase score.

The pain

The graduate did not recognize the charge and called the bank directly, because there was nobody to complain to.

With Partiu Formatura

With the feature on for the class, the app shows "Dispute charge" on the paid installment. The dispute has a protocol, a deadline and a conversation, and every one resolved there is a chargeback that never reached the bank.

The pain

The doorman got a paper list with twenty suspicious names and turned away three graduates who had already sorted everything out.

With Partiu Formatura

The warning appears at scan time, with the current reason. Only a lost chargeback blocks; everything else shows as "Check ID", and the person at the door decides with the document in hand.

The pain

A competitor antifraud tool froze ticket sales one night when its provider slowed down.

With Partiu Formatura

When in doubt, release. An unsubscribed module, an error or a delay above the limit let the sale go through and record the failure. A small fraud costs less than a whole batch of graduates without tickets.

How it works

The path of a sale, from approved payment to delivery or dispute

  1. 1

    The payment is approved

    Card, pix or bank slip confirm through the usual route. The money comes in normally, and nothing in the module touches the installment.

  2. 2

    The gate reviews before delivery

    Before issuing the ticket, sending the order to shipping or activating the consumption credit, the engine reads signals from the database itself and computes the score, with the sentence for every signal that fired.

  3. 3

    The rule decides

    Release right away, hold above the limit, always review or hold for a few hours. In observation mode the decision is recorded and the sale goes through.

  4. 4

    Someone looks, or the deadline decides

    The held purchase enters the queue with a deadline. Approving releases delivery immediately; rejecting keeps it held; without a decision, the routine applies what the rule says on expiry.

  5. 5

    The entrance checks

    On event day, the validation app shows "Check ID" for purchases approved with a caveat, high risk or an open dispute, and only blocks when the payment has already gone back to the card.

  6. 6

    The dispute is defended with proof

    If a chargeback arrives, the case is created with a deadline, the evidence package is generated in minutes and the result goes into the losses avoided report.

How the system behaves

12 decisions that explain everything else

They explain why the system sometimes does not do what you might expect, and why that is intentional.

Money is never held

The module does not decline payments, does not refund and does not touch installments. It holds the delivery. Declining payment would push the legitimate graduate to another method, and refunding on its own would take the decision away from whoever has the authority to return money.

When in doubt, release

An unsubscribed module, a missing table, an engine error or a delay above six seconds release the sale and record the failure. An antifraud tool that freezes sales when it fails itself becomes the biggest risk in the operation.

It starts by observing

Subscribing to the module does not hold any purchase. It reviews, shows what it would have held and waits for someone to switch holding on after seeing the impact. An antifraud rule turned on without calibration is the fastest way to lose good customers.

No score without a reason

Every score point comes from a signal with a sentence. The reviewer decides by reading the reason, and the same sentence goes into the evidence package. An opaque number is useless for approving and for defending.

Default rules live in code

Weights, bands and ready rules need no setup. The table stores only what the company changed, and going back to the default deletes the change instead of copying the value: that way a future improvement reaches whoever did not customize.

Holds have a deadline

A queue without a deadline becomes a forgotten queue. Tickets release on expiry because events have dates; physical products stay held because a shipped box does not come back.

The same purchase is reviewed once

The automatic check of paid orders runs every hour. The second pass reads the decision that already exists, and a purchase with several tickets is reviewed only once, by installment.

A card is BIN and last digits

The card number is not requested, not accepted on the list and not stored. BIN and last digits are enough to see the same card circulating between accounts.

The entrance decides with the ID in hand

The system warns and explains; the person at the door decides. Automatic blocking is limited to the undisputed case: the payment already went back to the card.

Evidence sent never changes

Each package generation is a new version with SHA-256. What went to the acquirer has to stay the same when someone asks months later.

Absence is information too

A section without proof is included and flagged as missing. Knowing there is no proof of delivery changes the decision between disputing and accepting.

Graduate disputes are optional

Not every company wants graduates disputing through the app. The feature starts off, is enabled per class, and the server refuses new disputes when it is off, without relying only on hiding the button.

The boundaries

Where the module touches the rest of the platform

The module never keeps a second copy of anything. It reads what already exists and returns what it produced through the same path as the rest of the platform.

Tickets

Issuing goes through review before the reservation, and the three entrance validations return the risk warning.

Albums, store and shipping

A paid album, gallery product or store order is reviewed before entering the picking queue, and a held one only enters when review releases it.

Finance and payments

Installment, gateway log and card feed the signals; refunds stay in the Finance cancel transaction action.

Contracts

Signatures and acceptances with IP and a hash chained trail go into the evidence package.

Graduate app

Billing disputes appear on the paid installment when the feature is on for the class.

Governance

Who sees what, and what runs without anyone asking

4 separate permissions

Seven dedicated permissions, so each person only sees the part of the module they use. Reading the queue is open to reviewers without being leadership, and the evidence package has a separate permission for the legal team.

  • LeadershipDashboard, simulation, duplicates and the losses avoided report.
  • FinanceReview held purchases, handle chargebacks and answer billing disputes.
  • LegalGenerate and download the evidence package.
  • Entrance and configurationEvent risk list, and rules, mode, bands, weights and lists for whoever configures.

What runs on its own

An hourly routine keeps the module moving without anyone remembering the queue. Each warning is issued once, and running twice in the same hour repeats nothing.

  • Review at issuingEvery paid ticket issue, including the one done by the automatic check of paid orders, goes through review before creating the ticket.
  • Review at shippingBefore each intake, paid store, gallery product and album orders are reviewed, and held ones stay out of the queue.
  • Rule waiting timeA sale held for a few hours is released when the time passes without anyone holding it.
  • Review deadlineAn overdue review releases or stays held according to the rule, and the expiry is recorded.
  • Chargeback on webhookA dispute notice from the gateways becomes a case the same minute, without delaying payment processing.
  • Dispute deadlineA chargeback without a defense and a deadline within three days gets a timeline note, once a day.
  • Unanswered billing disputeA graduate dispute past its deadline is flagged, because unanswered disputes tend to become chargebacks.

In practice

4 everyday situations, from problem to result

01

The card tested the night before the show

The scenario

When ball ticket sales opened, an account created minutes earlier tried four declined cards and got the fifth approved, buying eight tickets at once.

With the system

The score added declines in the last hour, a new account and an amount far above the median. The purchase went to review, the reviewer saw a cardholder with no relation to the buyer and rejected it, blocking the card and the IP.

The result

The tickets were never issued, and when the cardholder chargeback arrived weeks later there was no event entry to explain.

02

Calibrating before switching on

The scenario

Leadership wanted to turn antifraud on, and support was afraid of a flood of graduates without tickets.

With the system

In observation mode, the dashboard showed the default rule would have held nineteen out of one thousand two hundred sales in thirty days, mostly accounts with no class link. The ticket score limit was adjusted before switching on.

The result

Holding started with a known impact, and the false positive rate became part of the report.

03

The dispute over a delivered album

The scenario

A buyer disputed a card charge claiming the album never arrived, three months after delivery.

With the system

The case came in through the gateway notice with a ten day deadline. The evidence package brought the contract acceptance with IP, the payment with the device used and the tracking with the delivery date.

The result

The defense was sent in one day, the dispute was won and the recovered amount went into the losses avoided report.

04

The double charge that never became a chargeback

The scenario

An installment was paid twice by a repeated click, and the graduate mother did not recognize the second charge.

With the system

With disputes enabled for the class, she opened one in the app, got a protocol and, the next day, an answer in her favor. Finance refunded the second installment through the usual path.

The result

The dispute was resolved without going through the bank, and the duplicates screen started showing double payments before anyone complained.

Glossary

Fraud and dispute terms, explained

The admin panel is written in Portuguese. If you came looking for payment industry terms, this is what each of them is inside the module.

ChargebackCard dispute
The cardholder request to the issuing bank to reverse a purchase. The amount leaves the company account until the dispute is decided.
DisputeRepresentment
The process in which the company contests the chargeback by sending proof to the acquirer, within a deadline.
Risk scoreScore
The number from 0 to 100 summed from the signals that fired on the sale, with low, medium and high bands.
SignalRisk signal
A verifiable fact about the sale that changes the risk, such as an account created minutes ago or a card used by another account. Each signal has a weight and a sentence.
HoldDelivery hold
The delivery held while waiting for a decision. The payment is not affected.
Observation modeShadow mode
The module reviews and records what it would have held, without holding. It is how the rule is calibrated before it applies.
False positiveWrongly held sale
A held purchase that was legitimate. The rate measures how much the rule gets in the way of good customers.
BINBank identification number
The first six to eight card digits, which identify the issuer. With the last digits, they identify the card without storing the number.
Card testingCarding
Several attempts in a row with different cards until one is approved, typical of cards obtained from leaks.
Evidence packageRepresentment package
The document that proves the purchase, ownership, use and delivery, sent to the acquirer as the defense.
SHA-256File hash
The fingerprint of the PDF. If a single character changes, the hash changes, so it is possible to prove the document sent is the one stored.
Billing disputePre-dispute
A complaint made directly to the company, before the customer goes to the bank. Resolved there, it does not become a chargeback.
Chargeback rateChargeback ratio
Disputes opened in the month divided by card payments in the month. Acquirers monitor and penalize high rates.

FAQ

The questions that come up when evaluating the module

Can the antifraud module decline a graduate payment?

No. The payment follows the usual path. What may wait for review is the delivery: issuing the ticket, sending the order to shipping or activating the consumption credit. The one who actually holds money is the bank in a chargeback, which is what the dispute side is for.

Do I need to configure anything to start?

No. Signals, weights and rules come ready, and the dashboard shows the simulation with real sales from the first minute. The module starts in observation, and switching holding on is a decision made while looking at the impact.

What if antifraud goes down on the night sales open?

The sale goes through. An error, a delay above the limit or unavailability release the delivery and leave a record. At the entrance, the risk lookup has a 1.5 second limit and, without an answer, validation works as usual.

Does rejecting a purchase refund the money?

No, on purpose. Delivery stays held and the screen points to the installment for the refund, which is still done in Finance, with the authority and the record of whoever returns money.

Which gateways record chargebacks on their own?

Asaas, Stripe and Mercado Pago. Rede, Cielo, Stone and other acquirers notify through a portal or email, and the case is recorded by picking the payment in a search, with no transaction code to type.

Can graduates dispute through the app without the company wanting it?

No. Disputes are an optional mobile feature, off by default and enabled per class. With it off, the button does not appear and the server refuses new disputes. Disputes already open stay trackable.

Will the doorman turn people away because of the score?

No. The warning is "Check ID", with the reason. The only automatic block is a payment that already went back to the card through a lost chargeback.

Is the card number stored anywhere?

No. The module works with the BIN and the last four digits, and the block list refuses a full number.

How do I know if the rules are too strict?

Through the false positive rate in the losses avoided report: the share of held purchases that were approved later. A high rate means the rule is holding legitimate graduates, and limits or weights are adjusted on the rules screen.

Keep exploring

The modules that work alongside this one

Compliance Control

Legal matrix, internal controls, risks and ethics channel. The integrity of the operation, next to the integrity of the money coming in.

View page

Incidents & Continuity

When a fraud attack becomes an operational problem, the incident coordinates the response with a commander and a timeline.

View page

Company Map

The links between class, contract, installment, event, ticket and gallery, navigable from the buyer of a suspicious purchase.

View page

Fewer chargebacks without a single legitimate graduate stopped at the door

We can open the module in observation with your real sales, run the simulation in front of you, show the review queue, the evidence package and the entrance warning, and talk about the right rules for your operation.

Talk to a specialistSee plans