# Mastercard 4834 - Point of Interaction Error
Source: https://paymentsandrisk.com/docs/reference/reason-codes/mastercard/poi-error

Last updated 24 October 2026.

Trying to add a tip before there's a dispute? Looking for [the payment and settlement checks](https://paymentsandrisk.com/docs/payments/appointment-fees/#the-tip-wont-settle)?

TL;DR

-   Something went wrong at the point of interaction: a duplicate charge, a wrong amount, a processing error at the terminal or on your site
-   Check the filing window for the specific processing error and region. Your merchant response date is on the notice
-   You win by showing only one transaction exists, that the two were separate legitimate sales, or that you already refunded the duplicate
-   Most 4834s trace back to your own batching or terminal config. Fix the cause, not the case

## Got this code?

**Your deadline:** The date on your notice wins. Ask your processor if it isn't clear: the network's issuer filing window isn't your response deadline.

**The claim:** The cardholder says a processing error happened at the terminal or on your site: a duplicate, a wrong amount or a late presentment.

**Records that answer it:**

1.  Which error was claimed: duplicate, wrong amount or late presentment?
2.  Transaction records comparing the auth and capture amounts
3.  Any refund of a duplicate

**Next:** [Decide whether it's worth fighting](https://paymentsandrisk.com/docs/chargebacks/your-first-chargeback/#should-you-fight-it), then build the response with the [Representment Workflow](https://paymentsandrisk.com/docs/operations/representment-workflow/).

## When This Code Applies

### Duplicate Processing

-   Same transaction submitted twice
-   Multiple authorizations cleared once each
-   Technical error caused duplicate

### Incorrect Amount

-   Cleared amount differs from authorized amount (beyond tolerance)
-   Wrong currency conversion
-   Incorrect tip/gratuity added

### Incorrect Transaction Code

-   Debit processed as credit (or vice versa)
-   Wrong transaction type indicator
-   Incorrect MCC used

### Late Presentment

-   Transaction cleared beyond allowable time frame
-   Delayed batch submission

### Currency/Conversion Errors

-   Wrong Dynamic Currency Conversion (DCC) rate
-   Incorrect currency code
-   Conversion applied when not requested

## Error Subcategories

### 4834.1 - Duplicate Processing

**Conditions:**

-   Two or more clearing records for same transaction
-   Same amount, same date, same merchant
-   Only one authorization obtained

**Time frame:** 90 calendar days from duplicate transaction date

### 4834.2 - Incorrect Amount

**Conditions:**

-   Cleared amount exceeds authorized amount
-   Beyond the tolerance applicable to this transaction
-   No valid reason for difference

**Tolerances:**

| Transaction Type | Tolerance to check |
| --- | --- |
| US card-present | Ask for the current gratuity rule and any chip/PIN or final-authorization exclusion |
| US CNP restaurants | Confirm the eligible MCC and authorization type |
| All other | Check the applicable transaction and regional rule |

The [4808 authorization page](https://paymentsandrisk.com/docs/reference/reason-codes/mastercard/authorization/#gratuity-tolerances) distinguishes gratuity conditions. Don't apply a flat 20% to every transaction.

### 4834.3 - Late Presentment

**Conditions:**

-   Transaction cleared beyond protection period
-   No valid authorization at time of clearing
-   Exceeded network time frames

**Protection periods:**

| Transaction Type | Window |
| --- | --- |
| Standard | 7 calendar days |
| Preauthorization | 30 calendar days |
| Car rental/hotel | 30 calendar days |

### 4834.4 - Incorrect Currency

**Conditions:**

-   Transaction currency doesn't match authorization
-   DCC applied without cardholder consent
-   Wrong conversion rate used

## Time Frames

| Region | Chargeback Window |
| --- | --- |
| Standard | Confirm the processing-error condition and start event |
| Duplicate | Confirm the duplicate-processing rule and start event |
| Europe ATM/Maestro | Confirm the product and regional rule |

Use the response date on your notice. The network's issuer filing window isn't your merchant response deadline. Ask your acquirer for the current condition, regional rule and edition before relying on a filing-window summary.

## Representment Options

### For Duplicate Processing

**Valid defenses:**

-   Only one transaction exists (mistaken chargeback)
-   Two separate, legitimate transactions
-   Refund already issued for duplicate

**Evidence required:**

-   Transaction receipts showing different transactions
-   Proof of refund
-   Authorization records showing separate auths

### For Incorrect Amount

**Valid defenses:**

-   Amount is correct per authorization
-   Cardholder agreed to final amount
-   Gratuity was within tolerance
-   Additional authorized charges (addendum)

**Evidence required:**

-   Signed receipt with final amount
-   Authorization showing correct amount
-   Cardholder agreement to charges

### For Late Presentment

**Valid defenses:**

-   Transaction was presented on time
-   Valid authorization existed
-   Within protection period

**Evidence required:**

-   Clearing date documentation
-   Authorization record with date
-   Batch submission records

### For Incorrect Currency

**Valid defenses:**

-   Cardholder chose DCC
-   Currency was correct
-   Conversion was accurate

**Evidence required:**

-   DCC disclosure signed by cardholder
-   Receipt showing currency choice
-   Exchange rate documentation

## Second Presentment Time Frames

| Region | Window |
| --- | --- |
| Standard | 45 calendar days |
| Costa Rica | 10 calendar days |
| Kazakhstan | 30 calendar days |
| Nigeria | **2 business days** |
| Tanzania | 20 calendar days |

## Which defenses hold up

| Error Type | With Evidence | Without Evidence |
| --- | --- | --- |
| Duplicate (refund issued) | Refund record shows the duplicate was credited | Can't show the duplicate was credited |
| Amount (receipt signed) | Signed receipt shows the agreed amount | Can't show agreement to the amount |
| Late presentment | Clearing and authorization records support timely presentment | Can't show the transaction was presented on time |
| Currency (DCC consent) | Signed disclosure shows the cardholder chose DCC | Can't show consent to DCC |

Track your own [win rate by reason code](https://paymentsandrisk.com/docs/chargebacks/metrics/) instead of relying on a general figure.

## Common Mistakes

1.  **No batch reconciliation** - Duplicates slip through
2.  **Manual tip entry errors** - Fat fingers
3.  **Delayed settlements** - Batches sit too long
4.  **No DCC documentation** - Can't prove consent
5.  **Exceeding tolerances** - Not monitoring differences

## Related Codes

-   [4808](https://paymentsandrisk.com/docs/reference/reason-codes/mastercard/authorization/) - Authorization-Related
-   [4853](https://paymentsandrisk.com/docs/reference/reason-codes/mastercard/cardholder-dispute/) - Cardholder Dispute

## Prevention Strategies

### Preventing Duplicates

1.  **Batch reconciliation** - Review before submission
2.  **Transaction IDs** - Unique identifiers per transaction
3.  **Real-time monitoring** - Catch duplicates immediately
4.  **Terminal configuration** - Prevent double-swipes
5.  **Staff training** - One swipe per transaction

### Preventing Amount Errors

1.  **Clear receipts** - Show amount before signature
2.  **Tip entry process** - Verify before settling
3.  **Authorization match** - Clear amount = auth amount
4.  **Tolerance monitoring** - Alert on discrepancies

### Preventing Late Presentment

1.  **Daily batch settlement** - Don't accumulate
2.  **Authorization timing** - Track expiration
3.  **Automated clearing** - Reduce manual delays
4.  **Exception reporting** - Flag aged transactions

### Preventing Currency Errors

1.  **DCC disclosure** - Clear cardholder choice
2.  **Rate transparency** - Show conversion details
3.  **Documentation** - Keep currency choice records
4.  **Training** - Staff understand DCC rules

## Next Steps

**Prevent future 4834 chargebacks:**

1.  Implement duplicate detection before settlement
2.  Reconcile batches daily → Catch errors early
3.  Train staff on tip adjustment procedures
4.  [Check operations checklist](https://paymentsandrisk.com/docs/operations/checklist/)

* * *

## See Also

-   [Authorization Best Practices](https://paymentsandrisk.com/docs/payments/)
-   [Decline Codes](https://paymentsandrisk.com/docs/reference/decline-codes/)