Chargeback notice case preparation
For Merchant chargeback case coordinators
Prepare transaction, dispute category, amount and response deadline from an acquirer chargeback notice with fields you can edit. Dispute filing external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- merchant name
- Example Harbor Repair - synthetic
- transaction reference
- DEMO-TRANSACTION-0042
- case reference
- DEMO-CASE-0042
- notice date
- 2026-09-30
- reason code
- DEMO-REASON_CODE-0042
- disputed amount
- 1250
- response deadline
- 2026-11-30
{
"merchant_name": "Example Harbor Repair - synthetic",
"transaction_reference": "DEMO-TRANSACTION-0042",
"case_reference": "DEMO-CASE-0042",
"notice_date": "2026-09-30",
"reason_code": "DEMO-REASON_CODE-0042",
"disputed_amount": 1250,
"response_deadline": "2026-11-30"
}A complete synthetic document with the visible values shown below. Real responses also include model-reported confidence, validation and result status. Test your own file with this schema.
When this work lands on your desk
An acquirer chargeback notice arrives for merchant chargeback case coordinators. The next step needs transaction, dispute category, amount and response deadline, recorded under the correct document reference before the information enters your accounting review queue.
A chargeback notice lists a response deadline earlier than a separate settlement date. Keep the deadline visible for a human case owner. This schema keeps the source labels and values explicit so the reviewer can resolve the issue before downstream use.
Start with the documents you already collect
- Acquirer chargeback notice PDFs
- Scanned or photographed acquirer chargeback notice pages
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
After checking merchant name, transaction reference, case reference, your application maps the reviewed record into your accounting review queue. Keep the original document reference with the result. Dispute filing external. Dokyumi processes one file with a saved schema; your application owns record matching, business rules and updates to other systems.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaChoose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.
| Field | Type | What to capture |
|---|---|---|
merchant_name | string | Merchant name exactly as printed in this acquirer chargeback notice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
transaction_reference | string | Transaction reference exactly as printed in this acquirer chargeback notice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
case_reference | string | Case reference exactly as printed in this acquirer chargeback notice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
notice_date | date | Notice date explicitly printed in this acquirer chargeback notice. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
reason_code | string | Reason code exactly as printed in this acquirer chargeback notice. Preserve identifiers and qualifiers; do not look up or infer missing information. |
disputed_amount | currency | Disputed amount explicitly labeled in this acquirer chargeback notice. Preserve its sign and stated currency; do not calculate a missing amount. |
response_deadline | date | Response deadline explicitly printed in this acquirer chargeback notice. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- A chargeback notice lists a response deadline earlier than a separate settlement date. Keep the deadline visible for a human case owner.
- Check notice date, response deadline against their own printed labels; leave an unstated date empty instead of deriving it.
- Check disputed amount for signs, decimal placement and stated currency before any downstream calculation or posting.
Prove the fit on a representative batch.
Test acquirer chargeback notice examples from the layouts your team actually receives. Include the exception described here: A chargeback notice lists a response deadline earlier than a separate settlement date. Keep the deadline visible for a human case owner. Compare the extracted merchant name, transaction reference, case reference and any line rows with a reviewer's checked reference before enabling downstream actions.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Add recurring extraction capacity when acquirer chargeback notice intake becomes routine. Reuse this field contract for layouts that express the same information; create a separate schema when the next document has different fields or review requirements.
For a tailored implementation
Discuss document volume, page lengths and schema setup for merchant chargeback case coordinators. Bring difficult acquirer chargeback notice samples and the review requirements your implementation must preserve.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about chargeback notice case preparation
Which fields can I capture from an acquirer chargeback notice?
The starter schema contains merchant name, transaction reference, case reference, notice date, reason code, disputed amount, response deadline. Edit those definitions and choose your required fields before saving. Array fields include defined sub-fields so row values have a validation structure.
What needs review in chargeback notice case preparation?
A chargeback notice lists a response deadline earlier than a separate settlement date. Keep the deadline visible for a human case owner. Check the original source alongside model-reported confidence and validation output; completion status describes the extraction result, not the business decision.
How does this data reach your accounting review queue?
Save the schema, then send one supported PDF or image to POST /api/v1/extract with its slug. The response contains the data, model-reported confidence, validation and result status. Your application maps reviewed values to the destination; upload-site submissions can use a configured webhook. Dispute filing external.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.