P07: Late Submission
P07 is an American Express chargeback reason code that falls under the Processing Errors category. To break it down, it means that a transaction was submitted for settlement too long after the original authorization was obtained. Amex sets strict deadlines for how fast a captured transaction needs to make it through the pipeline, and when those windows are missed, the cardholder’s bank has grounds to dispute the charge - even if the sale itself was legitimate.
What makes P07 especially frustrating is that the underlying transaction is usually valid. The goods were delivered, the service was rendered, the customer had no complaint. The problem isn’t what was charged - it’s when it was submitted. A processing delay, a batch that didn’t close on time, or a gap in your workflow can quietly create a chargeback liability that feels very out of proportion to the issue.
I’ll break down what triggers a P07 chargeback, how the timeline works, what your options are if you’ve already received one - and, most importantly - how to tighten up your processes so it doesn’t happen again.
What Triggers a P07 Chargeback in the First Place
A P07 chargeback depends on timing - it gets filed when a merchant submits a transaction too late - either after the original authorization has expired or after holding a pending charge on a customer’s account for too long.
When a customer’s card is authorized, that approval doesn’t last forever. Most card networks give that authorization a window of around 7 to 10 days before it expires. If a merchant submits the charge after that window closes, the transaction is no longer backed by a valid authorization. The bank sees that as a problem and the chargeback follows.
The second trigger is a long-held authorization. If a charge sits pending on a customer’s account for more than 30 days without being finalized, that’s another path to a P07. The customer has been watching a hold tie up their funds for weeks and at that point the card network sides with them.

These situations happen for understandable reasons. A service business might not charge until the work is complete and delays in delivery or project completion push the billing date back more than expected. Merchants selling backordered goods face the same problem - they authorize the card at checkout but they don’t fulfill the order for weeks.
Delayed billing is another common scenario. Some businesses batch their transactions manually or run billing cycles at the end of a month instead of processing in real time. That workflow can accidentally push a charge past the authorization expiration without anyone noticing until the chargeback arrives.
Card networks don’t weigh up the reason for the delay. A delayed shipment, a slow billing process, a staffing gap during the holidays - none of that changes the outcome. Once the deadline passes, the transaction is treated as unauthorized regardless of intent.
It’s also worth mentioning that the customer doesn’t need to dispute the charge itself to trigger this. The bank or card network can initiate a P07 chargeback based purely on the timeline - even if the customer is happy with their purchase. That’s what makes late submission different from a common fraud or dispute chargeback - the transaction itself isn’t necessarily wrong, just the timing of it.
The Key Deadlines Every Merchant Should Know
P07 disputes run on a strict schedule, and the timelines are shorter than most merchants expect. Missing even one window can close the door on your options entirely.
Start with authorization validity. When a customer’s card is authorized at the point of sale, that authorization is only valid for 7 to 10 days. If you wait too long to capture the payment - say, because of a delayed shipment or a back-ordered item - you’re settling against an expired authorization; it’s one of the fastest ways to land a P07 chargeback.
Then there’s the 30-day hold rule. Card networks expect merchants to capture funds within 30 days of the original transaction date. If you miss that window, the transaction is considered late by definition, and the cardholder’s bank has good grounds to dispute the charge. There’s no wiggle room here.
Once a chargeback is filed, you have 20 days to respond with a rebuttal and supporting documents. That sounds like enough, but it goes fast when you need to track down receipts, pull order records, and write a response letter. Get your documentation process in order before you ever need it.
The full resolution timeline - from the second a chargeback is filed to a final decision - runs anywhere from 40 to 60 days; during that time your funds are on hold and your chargeback ratio is taking a hit. If you’re wondering what happens if you never reply to a credit card dispute, the answer is almost always an automatic loss.
| Event | Timeframe |
|---|---|
| Authorization validity window | 7-10 days from authorization |
| Maximum capture window | 30 days from transaction date |
| Merchant response window | 20 days from chargeback filing |
| Full resolution timeline | 40-60 days from chargeback filing |
The most important thing to know is that the deadlines stack on top of each other. A late capture can cause a chargeback, which then triggers its own response window, and the clock starts the second the dispute lands - not when you see it.
How to Fight a P07 Chargeback (and When It’s Worth It)
Once a P07 chargeback lands, that 20-day window moves fast. Your first job is to pull together evidence that proves the transaction was submitted on time and processed correctly.
The strongest evidence you can submit includes your authorization records, transaction timestamps, and any signed receipts with the sale. If you communicated with the cardholder before or after the transaction, include those logs too. You want to build a timeline that shows the card network when everything happened.
Authorization records are especially helpful here. They show that the bank approved the transaction at a date and time, which directly counters a late submission claim. If your timestamp falls within the allowed window, that single document can carry weight in your dispute response.
That said, not every chargeback is worth fighting. Before you put together a response, take an honest look at the situation. If the transaction was submitted late and you don’t have documentation to prove otherwise, disputing it will probably cost you more in time and fees than just accepting the loss.

An easy way to remember it:
| Situation | Worth Disputing? |
|---|---|
| You have timestamps showing submission within the allowed window | Yes - submit authorization records and timestamps |
| The transaction was submitted late | No - accept the chargeback and move on |
| You have signed receipts but no submission timestamp | Possibly - submit what you have but the outcome is uncertain |
| The disputed amount is very small | No - the cost to dispute may exceed the recovery |
A dispute that goes nowhere still costs you time to make and can affect your chargeback ratio if you lose - it’s worth a few minutes to weigh the evidence before filing a response.
If you do choose to fight it, keep your response clear and document-focused. Card networks don’t need a long explanation - they need proof.
Processing Habits That Keep P07 Off Your Radar
Most late submission problems come down to process gaps - not bad intentions. Busy teams, manual workflows and payment systems that haven’t been updated in years all create the delays that card networks penalize. Small, steady changes to how you manage transactions day-to-day can make a real difference.
The most important habit to build is re-authorization. If a transaction sits for more than a few days before you capture it, the original authorization may have expired. Before you submit, check that it’s still valid - and if it isn’t, run a fresh one. This single step removes the danger.
Delayed billing is another area worth cleaning up. If your business charges customers after a service is delivered or a product ships, your billing policy should spell out when that charge will happen. Make this visible to customers at checkout and document it internally so your team follows the same timeline every time.
Here are some helpful habits to put in place:

- Set internal deadlines to capture authorized transactions within 24 to 48 hours of authorization.
- Use your payment platform’s alerts or dashboards to flag any transaction that hasn’t been captured yet.
- Schedule a weekly check of pending transactions so nothing sits too long without attention.
- Review your submission windows against your processor’s rules at least once a year - these limits can change.
- Train anyone who touches your payment system to understand why timing matters, not just what buttons to press.
Manual processes are especially vulnerable here. When submission depends on remembering to do it, things slip. Automating capture where possible - or at least creating reminders - takes the human error factor out of the equation.
It’s also worth doing a wider audit of your payment workflow every few months. Look at where transactions stall and whether your current system is built to manage your volume. A setup that worked fine two years ago might not hold up today - and neither will a payment gateway that hasn’t been reviewed in a while.
Merchants who see the fewest P07 chargebacks are the ones who treat submission timing as a scheduled part of their operations instead of an afterthought.
Staying Ahead of Late Submission Chargebacks
Take a few minutes to audit where your latest workflow stands. Look closely at any gaps between authorization, capture and settlement - especially for delayed fulfillment models, recurring billing, or manual processing queues. Those are the places where late submissions like to quietly pile up before anyone notices.

A few quick reminders:
- Process transactions promptly - don’t let authorized payments sit uncaptured.
- Know your card network deadlines - they vary, and exceeding them is the core issue.
- Flag high-risk scenarios early - pre-orders, backorders, and delayed shipments need extra attention.
- Review your payment platform settings - automation can close the gap on manual errors.
- Train your team - the people managing transactions should understand why speed matters.
Proactive attention to your processing timeline goes a long way. Stay ahead of the deadlines and P07 can become one less chargeback reason code you ever have to worry about.
FAQs
What is an American Express P07 chargeback reason code?
P07 is an Amex chargeback code under Processing Errors, meaning a transaction was submitted for settlement too long after the original authorization was obtained.
What triggers a P07 late submission chargeback?
P07 is triggered when a merchant submits a transaction after the authorization has expired (7-10 days) or holds a pending charge on a customer's account for more than 30 days.
How long do merchants have to respond to P07?
Merchants have 20 days to respond to a P07 chargeback with a rebuttal and supporting documentation such as authorization records and transaction timestamps.
Is it worth fighting a P07 chargeback?
It's worth disputing if you have timestamps proving submission within the allowed window. If the transaction was genuinely submitted late, accepting the loss is usually more cost-effective.
How can merchants prevent P07 chargebacks?
Capture authorized transactions within 24-48 hours, re-authorize expired holds before capturing, automate batch processing where possible, and regularly audit your payment workflow for timing gaps.
Call (844) NO-DISPUTES