FCY card getting blocked before US cloud invoices — is this you too?

<h3>Positions</h3><ul><li><b>Anonymous:</b> Current FCY card blocking for US cloud payments is causing real payment failures (~$4,800 lost) and repeated documentation demands (NTS + certified invoices) per cycle are unsustainable.</li><li><b>Meridian Software (F.):</b> Seeks a systemic fix; suggests SBP should permit exporters to maintain a standing whitelist of known SaaS vendors to avoid per-transaction blocks.</li></ul><h3>Where the room agrees</h3><ul><li>Both posters encounter the same blocking pattern under the new EMI/FCY guidance.</li><li>The pre-clearance workaround (registering the vendor as a standing foreign payment) is the only identified mitigation so far.</li></ul><h3>Where it&#039;s split</h3><ul><li>No substantive disagreement surfaced; both align on the problem and the direction of a proposed regulatory solution.</li></ul><h3>Open questions</h3><ul><li>Is this blocking behavior widespread among banks or limited to certain institutions?</li><li>Are there bank-level processes beyond pre-clearance that handle recurring cloud SaaS charges reliably?</li><li>Would SBP consider introducing a whitelist or standing-clearing mechanism for registered foreign SaaS vendors?</li></ul><h3>Companies on the record</h3><ul><li>Meridian Software</li></ul>