An escrow application provides a secure way for buyers and sellers to complete transactions, ensuring that both parties fulfill their obligations before the funds are released.

This guide will walk you through the implementation of an escrow service using the Blnk Ledger. You will learn how to set up and manage escrow accounts, monitor transaction statuses, and handle the release or return of funds based on predefined conditions.

We’ll learn about:

  1. Defining and creating your ledger structure
  2. Account creation
  3. Funding escrow accounts
  4. Releasing funds
  5. Refunding funds
  6. Best Practices (with Inflight)

​
1. Ledger structure

The entry point of the Blnk ledger system is ledger folders. These folders serve as a way to group and manage assets, accounts, and balances that fit your product or organization’s structure.

In this guide, we’ll use the following structure:

  • Escrow Ledger: Contains all escrow accounts for users.

The ledger structure is flexible and can be customized based on your specific needs. For instance, you could group by types of transactions (e.g., real estate, freelance work), or use a combination of both.

See also:

​
Creating an Escrow Ledger

View your ledgers in your terminal:

bash
blnk ledgers list

Always store the ledger_id in your database. You’ll need it for future operations related to this ledger.

​
2. Balance (escrow account) creation

Blnk uses the concept of ledger balances to manage accounts/balances in a ledger. In this example, we’ll create escrow accounts for two users in an escrow transaction — Alice (the sender) and Bob (the recipient). T

See also:

​
Creating an escrow account for User Alice

View your balances in your terminal:

bash
blnk balances list

The balance_id is crucial. Always store this in your database and associate it with the customer. You’ll use this ID for all future transactions involving this loyalty point account.

​
Creating an escrow account for User Bob

​
3. Funding escrow accounts

Customers can fund their escrow accounts. We’ll use the Inflight feature to manage funding transactions.

See also:

​
Funding Alice’s escrow account

View your transactions in your terminal:

bash
blnk transactions list

​
4. Releasing Funds

Once the conditions of the escrow are met, the funds can be released to the appropriate party.

​
Releasing funds from Alice to Bob

Ensure that all conditions of the escrow are met before releasing funds. This might involve manual checks or automated verification depending on your application’s requirements.

​
5. Refunding funds

If the conditions of the escrow are not met, the funds can be refunded to the original depositor.

​
Refunding funds back to Alice

Ensure that all conditions of the escrow are checked before processing a refund. This might involve manual checks or automated verification depending on your application’s requirements.

​
See also

Managing side effects with Inflight

A deep-dive guide into how to implement Inflight in your application.

​
Best Practices (with Inflight)

  1. Balance Checks: Ensure the source balance has enough funds to complete the transaction. Prevent the source balance from having a balance lower than the amount in its inflight_debit_balance.
  2. Available Balance Calculation: In your application, calculate the available balance to prevent users from accessing funds that are held in Inflight transactions. This can be done as follows: 
    const availableBalance = balance - inflight_debit_balance;
  3. Error Handling: Implement robust error handling in your Inflight process. If a commit or void operation fails, you may need to retry or escalate to manual intervention.
  4. Customer Communication: Implement a system to notify customers about the status of their transactions, especially when they’re held in inflight.
  5. Reconciliation: Regularly reconcile your internal records with Blnk’s transaction logs to ensure accuracy. Pay special attention to Inflight transactions. Blnk v1 will support reconciliation features built into the ledger, which can aid in this process.
  6. Webhook Authentication: In a production environment, implement a mechanism to verify that webhooks are genuinely from your payment provider. This helps in maintaining the integrity and security of your transaction processing.
  7. Idempotency: Ensure your webhook handler is idempotent. Providers may send the same webhook multiple times, so your system should handle duplicate notifications gracefully.
  8. Monitoring: Set up monitoring and alerting for your webhook endpoint and inflight transactions. This can help you quickly identify and respond to any issues in the payment verification process.

​
Need help?

We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool.

To ask questions or discuss issues, please join our Discord community.

Was this page helpful?

Expense managementSavings application