What are manual panelist rewards payments?
Manual panelist reward payments introduce a secure, auditable, and integrated workflow for processing panelist reward payments in markets not covered by our automated payment partners.
By securely processing panelist rewards payments, panel owners can:
Enhance security and compliance with a built-in, auditable payment process
Increase data accuracy by tracking and monitoring all transactions
Improve efficiency with a simplified and scalable rewards payment process
Increase panelist satisfaction by paying rewards on time
How do manual panelist rewards payments work?
To process reward payments manually, your panelist will first need to request the payout in the Panelist Offerwall. This will trigger the transaction to be in a Processing state.
In Cint Engage:
Navigate to the company and panel for which you’d like to process manual reward payments.
Select Payment Methods in the left-hand menu.
Select Add payment method and then Make a payout.

Download the CSV template, which will contain all payouts in the Processing state.

Once the file is generated, you will see the following notification, which will be updated automatically based on when you have downloaded the CSV file:

Once the file is downloaded, you are ready to process the rewards payments using an alternative payment method, such as locally accepted gift cards, a bank transfer, or a local payment service.
Update the CSV file by marking each transaction as Completed or Failed and save the file.
Upload the file to Cint Engage to ensure your transaction trail is up-to-date.

The uploaded file will be processed by Cint Engage, and the status of each payment will be updated so that panelists can keep track of their rewards payments. The panelist will receive an email notification about their payment, and if the payment has failed, it will automatically create a refund ledger entry.

How does Cint Engage ensure an audit trail of the transactions?
All file download and upload actions are logged with a timestamp and the name of the admin user who processed the file, ensuring full audibility.