---
title: "Discussion on \"Maker-Checker Workflow for Vendor Bank Details: A Build Guide\" | Hashnode"
description: "Discussion on \"Maker-Checker Workflow for Vendor Bank Details: A Build Guide\". A maker-checker workflow is the standard answer when one person should never be able to move money alone: one user proposes a change, a different user approves it, and the system refuses to let those"
url: "https://hashnode.com/posts/maker-checker-workflow-for-vendor-bank-details-a-build-guide/6afdaf93f8f7ed67bb1e1dae"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Maker-Checker Workflow for Vendor Bank Details: A Build Guide](https://disruptivestudio.hashnode.dev/maker-checker-workflow-for-vendor-bank-details-a-build-guide?utm_source=hashnode&utm_medium=feed)

A maker-checker workflow is the standard answer when one person should never be able to move money alone: one user proposes a change, a different user approves it, and the system refuses to let those

12h ago · 12 min read · disruptivestudio.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#architecture](https://hashnode.com/tag/architecture)
-   [#postgres](https://hashnode.com/tag/postgres)
-   [#fintech](https://hashnode.com/tag/fintech)

## Written by

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

@danielcruznet

  
[View profile](https://hashnode.com/@danielcruznet)

Entrepreneur for 20+ years and UX designer with a psychology background. Founder of Disruptive Studio, building custom software and Ariani,

In a world driven by digital transformation, I've etched an indelible mark as a pioneering entrepreneur, graphic maestro, and innovative inventor. From stirring the cryptographic sphere with groundbreaking inventions to transforming a startup into a multi-million-dollar software giant, my journey is a testament to an unstoppable pursuit of excellence. A seasoned UX expert with deep roots in psychology, I shape digital landscapes that resonate with users, blend aesthetics with functionality, and evoke emotions. With a robust history in sales and professional networking, I build meaningful relationships that create synergies. My mantra, "wealth is inevitable to the right mindset", mirrors my belief in the transformative power of a proactive outlook. With over two decades of entrepreneurship, my path is dotted with innovation, value creation, and leadership. Eager to know more? Let's connect.

## Responses 2

Markdown supported · ⌘↵ to post

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

[9h 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.
