Payment Mismatches
Understand transfers that cannot settle the intended invoice.
| Situation | Current behavior | Merchant action |
|---|---|---|
| Wrong amount | Transfer remains unmatched to the v3 invoice | Do not fulfill; investigate manually |
| Partial payments | Multiple transfers are not accumulated | Ask the customer not to send another transfer without support guidance |
| Overpayment / underpayment | Wrong amount remains unmatched; historical status names are not a recovery promise | Do not fulfill automatically |
| Wrong token or contract | Not eligible for the invoice | Investigate manually |
| Wrong network | Not visible to the configured watcher and not eligible | Investigate manually |
| Late transfer | A transfer after expiresAt is not eligible | Do not fulfill automatically |
| Duplicate transfer | Only the invoice's canonical matched transaction settles it | Reconcile the extra transfer manually |
BramaPay does not expose a merchant self-service “force match” guarantee. Never ask the customer to send again until you have checked the invoice and transaction history; a delayed pre-expiry transfer may still settle.