End to End Testing Requirements - Content Provider

1min

Once integration tasks have been completed, it's time to test end to end to ensure that everything is working properly before launch.  While your Client Implementation Team will supply you with more details on this task, we're including an overview of the process here so that you'll be able to review it and ask any questions that you may have in order to better understand the scope of the effort:
First, offers need to be created in our system. The sequence for this is first, merchants, followed by offers or merchant locations (in either order).  
Once your offers have been created and indexed in the system, a Triple Content Team member will create test transactions against those offers to confirm that matching is functioning properly with the offer construct / merchant information.
Once a transaction has been matched, Triple will move the transaction through the settlement lifecycle, to the PENDING_MERCHANT_APPROVAL state.
You will then use the Triple API to see the reward(s) in PENDING_MERCHANT_APPROVAL state, and update them appropriately, to DENIED_BY_MERCHANT (indicating that the reward will not be funded) and/or PENDING_MERCHANT_FUNDING (indicating that the reward will be funded).
Following reward transition, the Triple team will create a sample reporting file and invoice backup file to send your way for review.
Once this is done, we consider end to end testing complete.
Once end to end testing is completed, you'll get your keys - we'll share PROD credentials with you.
﻿

Updated 21 May 2024

Did this page help you?

Integration Overview - Content Provider

Integration Overview - Publisher / Portfolio Manager