End to End Testing Requirements - Publisher / Portfolio Manager

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, any publishers and programs required need to be created on the platform.
Next, cards need to be registered as well. This should occur as early as possible (reasoning detailed below).
Additionally, we should confirm subscription to our webhook messages prior to any transaction submission. This requires an initial subscription message sent to the webhook service, receipt of a confirmation URL and posting of that URL to confirm the subscription. Additional details are found here: Subscribe To Notifications﻿﻿
Next, transactions need to be submitted to Triple, aligned with those cards (and aligned with active offer content available in Sandbox). A note here is that in order to match any transactions with those cards, the timestamp of those transactions must occur after the timestamp when a card is enrolled with Triple. Otherwise, the transaction lands in a NOT_ENROLLED status as the card wasn't enrolled at the time of the transaction (this is why we want to create / enroll cards as soon as possible).
As needed, Triple can provide sample transaction payload information that would be matched on our side to create synthetic transactions to confirm matching (since often times test data doesn't match offers that we have live in our systems).
All transactions will land with a matching_status = "QUEUED" status while we run transactions through the matching engine. Matching can take some time, esp. in Sandbox. Once matching has been conducted, transactions will have a matching_status of "MATCHED" or "NO_ACTIVE_OFFER".
For any transactions that land in "MATCHED" status, you will receive a webhook message indicating that the transaction is in "PENDING_MERCHANT_APPROVAL" from a reward perspective. The trigger of this webhook message does require manual intervention from our side, so we need to coordinate this step.
Once you confirm receipt of the PENDING_MERCHANT_APPROVAL webhook message, we will then move the reward through the following states (you should receive webhook messages for each of these): PENDING_MERCHANT_FUNDING, PENDING_TRANSFER_TO_PUBLISHER, DISTRIBUTED_TO_PUBLISHER
Once you receive the DISTRIBUTED_TO_PUBLISHER webhook message, you will need to update the reward status to DISTRIBUTED_TO_CARDHOLDER to indicate that the rewards have been given to the consumer at the discretion of the publisher or according to the publisher's process (through an account transfer, storage in a stored value account, etc.)- We can then send the ACH backup file to your accounting team so that they can see what we would be sending them as a part of settlement
Once we receive the DISTRIBUTED_TO_CARDHOLDER update, we consider the lifecycle of the reward and transaction complete, and 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 Jun 2024
Did this page help you?
Integration Overview - Publisher / Portfolio Manager
Introduction to Triple API Endpoints and Webhooks