Sans la plateforme
Information about Antifraud & Chargeback lives in separate spreadsheets, and nobody knows which version is current.
Avec Partiu Formatura
10 modules share the same class, graduate and event records.
Platform and intelligence · Antifraud & Chargeback
Fewer fraud 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, computed before delivery. What passes the limit waits for review with a deadline, and money is never held: what waits is the ticket, the order or the credit. The module starts in observation and shows what it would have held before holding. Duplicate cards, CPFs, purchases and tickets surface in the database, chargebacks arrive automatically from Asaas, Stripe and Mercado Pago with a versioned PDF evidence package, the entrance sees an ID check warning, graduates can dispute charges in the app when the class has the feature on, and leadership follows losses avoided and the false positive rate.
Le problème et la solution
What changes when Antifraud & Chargeback works inside the platform
This is connected information about classes, graduates and events across 10 modules, replacing scattered spreadsheets and messages.
Sans la plateforme
Demander un chiffre prend du temps, parce qu’il faut croiser des données venues de plusieurs endroits.
Avec Partiu Formatura
Transaction Risk Score and Release Rules update together, with figures ready for the next meeting.
Sans la plateforme
Le processus dépend de qui est là ce jour-là, et son historique disparaît.
Avec Partiu Formatura
Tout le monde suit le même circuit, avec des actions consignées et des droits par rôle.
Sans la plateforme
Communiquer avec les autres services suppose d’exporter des tableurs et de resaisir les données.
Avec Partiu Formatura
Antifraud & Chargeback shares information directly with other areas of the platform.
Comment ça marche
How information moves through Antifraud & Chargeback
Chaque étape correspond à un module réel de ce domaine. Ce qu’elle produit passe à l’étape suivante sans que personne resaisisse la même information.
What is available in Antifraud & Chargeback
- Transaction Risk ScoreA number from 0 to 100 that always comes with the reason.12
- Release RulesWhen an approved payment becomes a ticket, a product or a credit.10
- Suspicious Purchase ReviewThe held sale, the reason and the decision that already carries out the consequence.12
- Duplicate BlockingRepeated purchases, extra tickets and duplicate records, in the score and in the database.8
- Block and Trust ListsData the company decided to hold or release on purpose.6
- Chargeback TrackingDispute, amount, deadline, reason and acquirer decision in one place.11
- Evidence PackageThe defense built from what the system already stores, and frozen.13
- Event Risk ListWhat the entrance needs to check, at scan time.8
- Disputes by GraduatesThe graduate talks to the company before talking to the bank.9
- Losses Avoided ReportThe number leadership needs to decide whether the rule is right.8
À la une
Fewer chargebacks without turning away real graduates
Every paid ticket, store order, gallery product, album and consumption purchase gets a score explained by signals before delivery. What passes the limit waits for review with a deadline, and money is never held. When a card chargeback arrives, the case is created with a deadline and the evidence package comes out in minutes.
Voir à l’œuvre- Sixteen risk signals, each with the sentence that explains why it fired
- Starts in observation: shows what it would have held before holding
- Automatic chargebacks from Asaas, Stripe and Mercado Pago
- "Check ID" warning at the entrance and optional disputes in the app
Transaction Risk Score
A number from 0 to 100 that always comes with the reason.
- Sixteen signals grouped into amount, frequency, device and IP, ownership, address, behavior, duplicates, lists and trust
- Amount far above the tenant median for that sale, with at least twenty sales as a base
- Several purchases by the same buyer in 24 hours and an identical purchase minutes earlier
- Several card declines in the last hour from the same buyer or IP, the card testing pattern
- The same IP paying for three or more accounts in 24 hours
- Cardholder sharing no surname with the buyer and a different cardholder CPF
- The same card, by BIN and last digits, used by other accounts
- Delivery to a state different from the registered one for physical products
- Account created less than one hour before the purchase
- A graduate with paid installments and no disputes lowers the score
- A failing signal is skipped and logged: it never zeroes or maxes out the number
- Adjustable low, medium and high bands, and an editable weight per signal, with the default always visible
Release Rules
When an approved payment becomes a ticket, a product or a credit.
- One rule for each sale type and payment method
- Four actions: release right away, hold above the score limit, always review and hold for a few hours
- An amount ceiling above which the sale is always reviewed
- Review deadline per rule and what happens on expiry: release or stay held
- Ready rules: cards by score, pix, bank slips and manual settlement released right away
- Tickets and consumption release on expiry; physical products stay held
- Customized rules flagged on screen, with a button to go back to the default
- Observation and holding modes, with the last thirty days impact before switching
- A buyer on the block list is held on any payment method
- History of every rule, band and weight change with author and date
Suspicious Purchase Review
The held sale, the reason and the decision that already carries out the consequence.
- A held ticket is not issued, a held order does not enter shipping, a held credit is not activated
- Queue ordered by the deadline due first, with filters by status, sale type and search
- Detail with each signal and the sentence that explains it
- What is held: event, ticket type and holder, order items and address
- Other purchases by the same buyer that already went through review
- Approving releases immediately: issues the ticket, sends the order to shipping or activates the credit
- Approve with a caveat: releases and flags the ticket for an ID check at the entrance
- Waiting for the customer, with a record of what was requested
- Reject with a reason and the option to block the CPF, email, card or IP
- Rejecting does not refund: the path to the refund shows the installment
- Two reviewers on the same case: only the first decision counts
- Timeline with internal notes
Duplicate Blocking
Repeated purchases, extra tickets and duplicate records, in the score and in the database.
- An identical purchase by the same buyer within fifteen minutes weighs on the new purchase score
- The same card paying for different graduates, with names and amounts
- The same CPF on several records, ignoring known test CPFs
- The same mobile number on three or more accounts
- Repeated ticket purchases on the same day, with the amount to refund
- More tickets issued than the quantity bought in the transaction
- Installments paid twice with the same amount and due date
- One click blocking from the item found, always with a reason
Block and Trust Lists
Data the company decided to hold or release on purpose.
- CPF, email, card by BIN and last digits, or IP
- Mandatory reason, shown in the review of every matching purchase
- Optional expiry, with expired items no longer applying on their own
- Data active on one list cannot enter the other without leaving the first
- Removal with a reason, without erasing history
- A full card number is never accepted or stored
Chargeback Tracking
Dispute, amount, deadline, reason and acquirer decision in one place.
- Automatic intake from Asaas, from Stripe dispute notices and from the Mercado Pago chargebacks topic
- The same notice sent again updates the case instead of duplicating it
- A late gateway notice does not reopen a case closed by hand
- Manual recording by picking the payment in a search by name, CPF or email
- Reason normalized into fraud, unrecognized, not received, duplicate, canceled and other
- Status: open, building defense, defense sent, won, lost, accepted or canceled
- Response deadline highlighted within three days and a daily note on the timeline
- An owner who takes on the defense, and the recovered amount when won
- The affected sale identified: ticket, store order or installment
- Buyers and cards with a past chargeback weigh on future purchase scores
- A dispute opened earlier by the graduate is linked to the chargeback on the same installment
Evidence Package
The defense built from what the system already stores, and frozen.
- Authorized payment with gateway, transaction, authorization, NSU and masked card
- Technical payment log with the IP and device of every event
- Account holder, creation date and latest app and portal access
- Contract signatures and acceptances with IP, device and a hash chained trail
- Ticket issued, use at the entrance and entrance scans
- Order in shipping, tracking and delivery date
- WhatsApp messages and support tickets from the buyer
- A section without proof flagged as missing, with the reason
- A warning when the defense is weak and accepting may cost less than disputing
- PDF with page numbers, version and SHA-256 stored for verification
- A new generation creates a new version; the one sent never changes
- Private storage, download through a temporary link and a record of who downloaded it
- Sent to acquirer marker, which moves the case to defense sent
Event Risk List
What the entrance needs to check, at scan time.
- Purchase approved with a caveat in review
- High risk purchase released without review
- Payment dispute in progress on the card
- Buyer on the block list
- Only a lost chargeback blocks entry
- "Check ID" warning when scanning by QR code, camera and typed code
- Risk lookup capped at 1.5 seconds: with no answer, the entrance works as usual
- Per event list in the admin panel, with reasons and a printable version
Disputes by Graduates
The graduate talks to the company before talking to the bank.
- Optional per class: enabled in the class mobile features, off by default
- "Dispute charge" button on the paid installment, only with the feature on
- Reasons: I do not recognize it, wrong amount, charged twice, canceled without a refund, not received
- Protocol generated on the server and a five day response deadline
- A second dispute on the same installment becomes a message on the first
- Conversation with the company, reply requests and internal notes the graduate never sees
- Decision for the graduate or keeping the charge, with the answer the graduate reads in the app
- An open dispute stays trackable even if the feature is switched off
- A warning when the dispute passes its deadline without an answer
Losses Avoided Report
The number leadership needs to decide whether the rule is right.
- Loss avoided: amount blocked plus amount recovered in disputes
- Lost in disputes and amount disputed in the period
- Chargeback rate over the month card payments
- False positive rate: held purchases that belonged to legitimate graduates
- Held, would have been held, released by deadline
- Billing disputes resolved before the bank and those that became chargebacks
- Series from three to twenty four months, with a chart and a printable version
- Parts not yet available on the account show as zero and flagged, never hidden
Liste de contrôle
Everything included in Antifraud & Chargeback
All 97 features in this area, grouped by module so you can compare systems item by item.
- Sixteen signals grouped into amount, frequency, device and IP, ownership, address, behavior, duplicates, lists and trust
- Amount far above the tenant median for that sale, with at least twenty sales as a base
- Several purchases by the same buyer in 24 hours and an identical purchase minutes earlier
- Several card declines in the last hour from the same buyer or IP, the card testing pattern
- The same IP paying for three or more accounts in 24 hours
- Cardholder sharing no surname with the buyer and a different cardholder CPF
- The same card, by BIN and last digits, used by other accounts
- Delivery to a state different from the registered one for physical products
- Account created less than one hour before the purchase
- A graduate with paid installments and no disputes lowers the score
- A failing signal is skipped and logged: it never zeroes or maxes out the number
- Adjustable low, medium and high bands, and an editable weight per signal, with the default always visible
- One rule for each sale type and payment method
- Four actions: release right away, hold above the score limit, always review and hold for a few hours
- An amount ceiling above which the sale is always reviewed
- Review deadline per rule and what happens on expiry: release or stay held
- Ready rules: cards by score, pix, bank slips and manual settlement released right away
- Tickets and consumption release on expiry; physical products stay held
- Customized rules flagged on screen, with a button to go back to the default
- Observation and holding modes, with the last thirty days impact before switching
- A buyer on the block list is held on any payment method
- History of every rule, band and weight change with author and date
- A held ticket is not issued, a held order does not enter shipping, a held credit is not activated
- Queue ordered by the deadline due first, with filters by status, sale type and search
- Detail with each signal and the sentence that explains it
- What is held: event, ticket type and holder, order items and address
- Other purchases by the same buyer that already went through review
- Approving releases immediately: issues the ticket, sends the order to shipping or activates the credit
- Approve with a caveat: releases and flags the ticket for an ID check at the entrance
- Waiting for the customer, with a record of what was requested
- Reject with a reason and the option to block the CPF, email, card or IP
- Rejecting does not refund: the path to the refund shows the installment
- Two reviewers on the same case: only the first decision counts
- Timeline with internal notes
- An identical purchase by the same buyer within fifteen minutes weighs on the new purchase score
- The same card paying for different graduates, with names and amounts
- The same CPF on several records, ignoring known test CPFs
- The same mobile number on three or more accounts
- Repeated ticket purchases on the same day, with the amount to refund
- More tickets issued than the quantity bought in the transaction
- Installments paid twice with the same amount and due date
- One click blocking from the item found, always with a reason
- CPF, email, card by BIN and last digits, or IP
- Mandatory reason, shown in the review of every matching purchase
- Optional expiry, with expired items no longer applying on their own
- Data active on one list cannot enter the other without leaving the first
- Removal with a reason, without erasing history
- A full card number is never accepted or stored
- Automatic intake from Asaas, from Stripe dispute notices and from the Mercado Pago chargebacks topic
- The same notice sent again updates the case instead of duplicating it
- A late gateway notice does not reopen a case closed by hand
- Manual recording by picking the payment in a search by name, CPF or email
- Reason normalized into fraud, unrecognized, not received, duplicate, canceled and other
- Status: open, building defense, defense sent, won, lost, accepted or canceled
- Response deadline highlighted within three days and a daily note on the timeline
- An owner who takes on the defense, and the recovered amount when won
- The affected sale identified: ticket, store order or installment
- Buyers and cards with a past chargeback weigh on future purchase scores
- A dispute opened earlier by the graduate is linked to the chargeback on the same installment
- Authorized payment with gateway, transaction, authorization, NSU and masked card
- Technical payment log with the IP and device of every event
- Account holder, creation date and latest app and portal access
- Contract signatures and acceptances with IP, device and a hash chained trail
- Ticket issued, use at the entrance and entrance scans
- Order in shipping, tracking and delivery date
- WhatsApp messages and support tickets from the buyer
- A section without proof flagged as missing, with the reason
- A warning when the defense is weak and accepting may cost less than disputing
- PDF with page numbers, version and SHA-256 stored for verification
- A new generation creates a new version; the one sent never changes
- Private storage, download through a temporary link and a record of who downloaded it
- Sent to acquirer marker, which moves the case to defense sent
- Purchase approved with a caveat in review
- High risk purchase released without review
- Payment dispute in progress on the card
- Buyer on the block list
- Only a lost chargeback blocks entry
- "Check ID" warning when scanning by QR code, camera and typed code
- Risk lookup capped at 1.5 seconds: with no answer, the entrance works as usual
- Per event list in the admin panel, with reasons and a printable version
- Optional per class: enabled in the class mobile features, off by default
- "Dispute charge" button on the paid installment, only with the feature on
- Reasons: I do not recognize it, wrong amount, charged twice, canceled without a refund, not received
- Protocol generated on the server and a five day response deadline
- A second dispute on the same installment becomes a message on the first
- Conversation with the company, reply requests and internal notes the graduate never sees
- Decision for the graduate or keeping the charge, with the answer the graduate reads in the app
- An open dispute stays trackable even if the feature is switched off
- A warning when the dispute passes its deadline without an answer
- Loss avoided: amount blocked plus amount recovered in disputes
- Lost in disputes and amount disputed in the period
- Chargeback rate over the month card payments
- False positive rate: held purchases that belonged to legitimate graduates
- Held, would have been held, released by deadline
- Billing disputes resolved before the bank and those that became chargebacks
- Series from three to twenty four months, with a chart and a printable version
- Parts not yet available on the account show as zero and flagged, never hidden
Want to see Antifraud & Chargeback in your operation?
Demandez une démonstration sur vos propres chiffres, sans engagement. Un échange vous aidera à juger si le module répond à vos besoins.