---
title: "Comment by Azhar Abbas on \"Maker-Checker Workflow for Vendor Bank Details: A Build Guide\" | Hashnode"
description: "Enforcing it at payment time is the part people skip. If the payment engine only pays accounts that came out of the approval flow, a CSV import or admin API can"
url: "https://hashnode.com/posts/maker-checker-workflow-for-vendor-bank-details-a-build-guide/6afdaf93f8f7ed67bb1e1dae/comment/6afdd8344d44544d9a51869c"
---

[Discussion](https://hashnode.com/posts/maker-checker-workflow-for-vendor-bank-details-a-build-guide/6afdaf93f8f7ed67bb1e1dae)

Comment [Maker-Checker Workflow for Vendor Bank Details: A Build Guide](https://hashnode.com/posts/maker-checker-workflow-for-vendor-bank-details-a-build-guide/6afdaf93f8f7ed67bb1e1dae)

[Azhar Abbas](https://hashnode.com/@azharabbas)

[10h ago](https://hashnode.com/posts/maker-checker-workflow-for-vendor-bank-details-a-build-guide/6afdaf93f8f7ed67bb1e1dae/comment/6afdd8344d44544d9a51869c)

Enforcing it at payment time is the part people skip. If the payment engine only pays accounts that came out of the approval flow, a CSV import or admin API can't quietly bypass the checker.

[Daniel Cruz](https://hashnode.com/@danielcruznet)

[9h ago](https://hashnode.com/posts/maker-checker-workflow-for-vendor-bank-details-a-build-guide/6afdaf93f8f7ed67bb1e1dae/comment/6afdd8344d44544d9a51869c#reply-6afddce31a015665c23f121b)

Thanks for pointing that out! Approval at edit time only proves someone looked at it once. The payment engine has to check again right before it writes the file: same approved version, still active. And with the rules enforced in the database as well, an import or an admin endpoint that skips the app still can’t get around the checker.
