14 January 2026
Answering a gateway’s follow-up without rewriting the file
When a payment gateway comes back with questions, the temptation is to produce a new narrative. That is how a file that was merely incomplete becomes inconsistent. The safer move is to answer with a pointer: exhibit, page, month, and one sentence.
Most follow-ups we see from platforms fall into three buckets. They cannot match a month. They cannot see who owns the entity. They cannot tell refunds from chargebacks. If your original pack was read before submission, those buckets are already labelled. The reply can be short.
Do not replace statements. Add a note. If a month was missing because the account was frozen for a week, say so and attach the bank letter. If a director changed, attach the SSM update and the dated resolution. If a chargeback was reversed, attach the representment outcome, not a new ratio with no trail.
Keep the same person talking. Gateways notice when the first pack was written by finance and the follow-up was written by a vendor who has not seen the statements. If we prepared the original findings memo, a follow-up reading is a separate, shorter engagement — we do not silently rewrite your answers as part of the first fee.
And if the honest answer is that you do not have the paper, say that. A delayed submission beats a confident sentence that the next reviewer will disprove in ten minutes.