Enabling Approval Workflows (Maker

Secure, Flexible, and Scalable Payment Governance

Approval Workflows (Maker–Checker) at Cobre enable businesses to control how and when money movements are executed by separating payment creation from payment approval. Cobre supports this capability natively in the Portal and also facilitates fully custom approval workflows via API, allowing companies to adapt governance to their internal processes.

This dual approach makes Cobre suitable for both out-of-the-box operational control and deeply customized enterprise workflows.

1. What Cobre Enables with Approval Workflows

With Maker–Checker, Cobre allows businesses to:

Centralize approvals in the Cobre Portal

Enforce separation of duties between creators and approvers

Require approvals for individual or bulk money movements

Apply dual control rules such as multiple approvers

Secure approvals with Multi-Factor Authentication (MFA)

Build custom approval logic using APIs

Approval workflows can be tailored to different risk levels, teams, and payment types.

2. Two Ways to Implement Maker–Checker at Cobre

Cobre supports approval workflows through two complementary models:

2.1 Native Maker–Checker in the Cobre Portal

The Cobre Portal includes a built-in Approval Section where authorized users can review, approve, or decline payments before execution.

This option is ideal for:

Finance and operations teams

Manual review processes

Organizations that want governance without building custom logic

2.2 Custom Approval Workflows via API

For clients that require bespoke approval logic, Cobre provides API support to build custom workflows.

From a capability standpoint:

Money movements can be flagged as requiring approval

Execution is paused until a decision is provided

A dedicated API allows clients to approve or reject the movement

Clients control:

Who approves

When approvals happen

How many approvals are required

Which systems participate in the decision

This enables integration with:

Internal ERP systems

Custom treasury platforms

Internal approval engines

Cobre acts as the execution and enforcement layer, while clients control the workflow logic.

3. Maker–Checker in the Cobre Portal

3.1 Approval Section

The Approval Section is a dedicated area in the Portal where users manage pending approvals.

Key capabilities:

View all payments that require action

Approve or decline individual payments

Approve or decline up to 50 payments at once

Manage batch-level approvals for bulk payments

Enforced MFA for all approval actions

This ensures both security and operational efficiency.

4. How Approvals Work in the Portal

4.1 Individual Money Movements

Whether a payment requires approval depends on user role and configuration:

Creator roles

Approval is always required

Creators cannot execute payments directly

Admin users

Can decide whether a payment:

Requires approval, or

Bypasses approval and executes directly

Payments marked as needing approval must be reviewed in the Approval Section.

4.2 Bulk Money Movements (Batch-Level Approvals)

For bulk payments, approvals are managed at the batch level.

How it works:

When a bulk file is uploaded, the batch is marked as Pending Approval

All associated payments default to Need Approval, unless already decided

Approving or declining a batch:

Affects only payments without prior decisions

Does not override approved or declined payments

This allows efficient governance of large payout operations.

5. Approval States

Payments under Maker–Checker move through clear states:

State	Description
Need Approval	Payment is awaiting a decision
Approved & Processing	Payment was approved and is being executed
Cancelled	Payment was declined and will not execute

These states provide transparency for both operators and auditors.

6. Dual Control Rules (Portal only)

Approval workflows integrate with Dual Control Rules, which allow businesses to further customize governance.

What this enables:

Require multiple approvers for payments requested by administrators

Dual Control Rules are configured in the Security section of the Portal and apply automatically during approvals.

7. Roles, Permissions & Security (Portal only)

Approval workflows are enforced through role-based permissions:

Creators

Can initiate payments

Cannot approve

Approvers / Admins

Can approve or decline payments

Can act at individual or batch level

All approval actions require Multi-Factor Authentication (MFA), including batch-level decisions.

This ensures approvals are both intentional and auditable.

8. Approval Workflows at Scale

Maker–Checker works seamlessly with advanced Cobre capabilities:

Bulk Money Movements

One decision can govern hundreds or thousands of payments

Scheduled Money Movements

Approval can occur at scheduling time

Execution happens automatically later

This allows companies to scale operations without weakening controls.

9. Portal-Based vs API-Based Approvals

From a capability perspective:

Dimension	Portal Approval	API-Based Approval
Setup	Ready out of the box	Fully customizable
UI	Cobre Portal	Client-owned UI
Logic	Up to 5 approvers can be configured	Client-defined logic
Scale	High	Very high
Best for	Ops & finance teams	Enterprises with internal systems

Cobre supports both models simultaneously, giving clients flexibility as they grow.

10. Summary — What Cobre Delivers with Approval Workflows

With Approval Workflows (Maker–Checker), Cobre enables:

Native Maker–Checker in the Portal
Custom-built approval workflows via API
Individual and batch-level approvals
MFA-secured decision making
Dual control and multi-approver rules
Full auditability and traceability

Cobre embeds governance directly into its money movement platform while also enabling custom enterprise-grade workflows, allowing businesses to operate with control, flexibility, and confidence.

Enabling Approval Workflows (Maker–Checker)

Secure, Flexible, and Scalable Payment Governance#

1. What Cobre Enables with Approval Workflows#

2. Two Ways to Implement Maker–Checker at Cobre#

2.1 Native Maker–Checker in the Cobre Portal#

2.2 Custom Approval Workflows via API#

3. Maker–Checker in the Cobre Portal#

3.1 Approval Section#

4. How Approvals Work in the Portal#

4.1 Individual Money Movements#

4.2 Bulk Money Movements (Batch-Level Approvals)#

5. Approval States#

6. Dual Control Rules (Portal only)#

7. Roles, Permissions & Security (Portal only)#

8. Approval Workflows at Scale#

9. Portal-Based vs API-Based Approvals#

10. Summary — What Cobre Delivers with Approval Workflows#