Overview
The Maker-Checker feature adds an approval layer to changes made in a publisher's billing section. Instead of changes taking effect immediately, they are held in a pending state until a designated checker reviews and approves or rejects them.
This article explains how Maker-Checker works, how to configure it, and how checkers can manage approval requests.
What is Maker-Checker?
Maker-Checker is a two-step authorization workflow designed to protect sensitive publisher billing information from unauthorized or accidental changes. When enabled, any modification made to a publisher's billing details is not applied immediately it is placed in a pending state and must be approved by a pre-designated team member (the checker) before it takes effect.
This is particularly useful for networks that handle large volumes of publisher payments and need an internal control mechanism to prevent billing errors or unauthorised edits.
When this feature is enabled, every admin will have access to two options in their profile section:
1. Maker-Checker
2. Approval Requests
How It Works
Once Maker-Checker is enabled, every admin on the panel gains access to two sections in their profile:
Maker-Checker : Where admins set up checker rules by assigning a team member as the approver for specific billing field changes
Approval Requests: Where pending, approved, and rejected change requests are listed and managed
1. Maker checker : Here you can select a user to be a checker of pending approval requests.
For example: If you'd like xyz user to review publisher banking details, simply select them, choose their type, status, fields, and then press the 'Save' button. This will allow xyz user to validate any changes made to the publisher banking details.
2. Approval Requests: When you go to the approval request, you will be able to see a list of all of your pending approval requests, as well as those that have been rejected and approved.
* If any changes have been made, they will be reflected here as pending, and you will have access to all of the details. If you click on the click here option below the details section, you can see the original details as well as the changes that have been proposed.
* If the changes appear to be acceptable, you can approve them and the changes will appear in the publisher banking details.
* If you decide to reject the pending status you must give a reason and select the Yes, Reject option; the changes will then not be implemented.
Note: For the time being we only have limited criterion for maker checker but we are open to add more on custom request and for that please reach out to CSM.
Why Use Maker-Checker?
Prevent unauthorized or accidental changes to publisher banking and billing details
Create a clear audit trail of all proposed and approved billing changes
Assign accountability by designating specific team members as approvers
Reduce billing disputes and payment errors caused by unverified data changes
Maintain compliance with internal financial controls and approval processes
Conclusion
Maker-Checker gives networks a simple but powerful internal control mechanism for managing changes to sensitive publisher billing information. By requiring a designated approver to validate every change before it takes effect, you reduce the risk of billing errors, maintain a clear audit trail, and ensure accountability across your team for all financial data updates.
Need Instant Resolution?
We want to assure our customers that Trackier provides an in-house customer support team, available for instant query resolutions. You can reach out to us via email at support@trackier.com or directly engage with our in-house agents through our live chat feature.
