Merchant use cases with solutions using webhooks and API calls
Merchant Use Cases
Below are some scenarios in which merchants have asked ChargeAfter how using webhooks and API calls can help them gather specific information to achieve various goals.
Use Case #1: Prequalified Without Application Completion
Q: I'd like to contact potential consumers who were prequalified but did not complete an application. How can ChargeAfter help me see those consumers?
A: Subscribe to the application.prequalified webhook to gather applicationId
s of applications that were prequalified. You could match these against applicationId
s of completed applications, provided in the application.apply-confirmed and application.checkout-confirmed webhooks to determine which applications did not complete the process.
Use Case #2: Approved Without Checkout
Q: I'd like to contact potential consumers who were approved but did not check out. How can ChargeAfter help me see those consumers?
A: Step 1: The application.approved webhook is sent when a lender approves an account. This would allow the merchant to gather applicationId
s of all consumers with approved accounts. The merchant would then need to match applicationId
s with consumerId
s. You can use the Get status of an application API call to send applicationId
s and receive consumerId
s in return.
Step 2: Subscribe to the postsale.authorize.accepted webhook to gather chargeId
s.
Using the Get details of a Charge API call, send the chargeId
s to receive consumerId
s in return of the consumers who completed a checkout.
Step 3: The two sets of consumerId
s can be checked against each other to identify the remaining consumers who were approved but did not check out.
Use Case #3: Remaining Balance on Line of Credit
Q: I'd like to contact existing consumers who have an available balance on their line of credit so I can encourage them to use that balance on another purchase. How can I identify those consumers?
A: You can use the Get status of an application API call to see the availableCredit
(nested in the creditInfo
object) by consumerId
. You will need to provide the applicationId
to send a request.
Using Webhooks vs. Callbacks
If a merchant is not integrated with the SDK and cannot make use of the SDK callbacks, then the merchant can subscribe to webhooks to receive notifications about relevant events.
The table below maps callbacks to webhooks.
Callback | Webhook |
---|---|
onModalOpen | No equivalent webhook, as the callback relates to modal opening. |
onApplicationCreated | application.created |
onDataUpdate Note: This is sent when consumer details are updated. | links.checkout-data-update Note: This is sent when cart information is updated. |
onConfirm | application.checkout-confirmed Note: This webhook returns a token IF the checkout is in the Apply and Buy Now flow. |
callback (Completion) | No equivalent webhook, as the callback relates to modal closure. |