Introduction

What is a Policy?

A policy is a set of rules that defines how certain actions in the system should be handled based on your business needs. Instead of having these rules permanently built into the application, policies allow you to control behavior through configurable logic.


Why Do We Need Policies?

Every merchant operates differently. Business rules such as who can perform a transfer, where funds can be sent, or which provider should be used may vary from one merchant to another and they may also change over time.

Without policies, any change to these rules would require changes to the application itself, followed by testing and redeployment. Policies remove this dependency by allowing merchants to adjust specific behaviors without changing the underlying system.

This approach gives you:

  • Greater flexibility to match your business processes
  • Faster updates to rules without system downtime
  • Clear separation between platform functionality and merchant-specific rules

How Do Policies Work?

The application continues to handle all core processes, such as:

  • Validating source and destination accounts
  • Checking wallet limits and active transactions
  • Communicating with payment or transfer providers

Once all required data is gathered, the system evaluates the policy rules you have defined to decide whether an action should proceed.

For example, a policy can be used to:

  • Allow transfers only for specific user roles
  • Restrict transfers to approved destination accounts
  • Enforce the use of a specific provider for certain transactions

All of these rules can be updated through policies without modifying the application code, giving you control over how the system behaves while the platform ensures secure and reliable execution.