Redirection after a successful Customer Workflow
The Redirection after a successful workflow setting is a way to customize the end step of a Customer Workflow, that can be found in Settings / Hosted Pages / Customer Workflows.
This setting has two purposes:
- Fluidify the customer experience, for example, by sending your new subscribers to a specific page.
- Perform customized actions whenever a subscription-billing process ends, like refreshing the user’s rights.
Querystring parameters
Section titled “Querystring parameters”Here are the parameters added to the redirection URL.
| Parameter | Description | Detail |
|---|---|---|
| from | See the list below for all the possible values. | Always present |
| outcome | See the list below for all the possible values. | Always present |
| idc | (for idCustomer) Internal identifier of the Customer in ProAbono. For security reasons, the shared identifier (ReferenceCustomer) is not used. | Always present |
| refo | (for ReferenceOffer) Reference of the related Offer. | Only if relevant |
| idsub | (for idSubscription) Internal identifier of the Subscription in ProAbono. | Only if relevant |
Values of the ‘from’ parameter
Section titled “Values of the ‘from’ parameter”This parameter indicates what workflow the customer just completed. It’s useful to display the right message or perform the correct post-processing.
| Value | Description |
|---|---|
| subscribe | The customer just subscribed. |
| upgrade | The customer changed its plan. |
| restart | The customer restarted its suspended subscription. |
| options | The customer changed the options of its subscription. |
| terminate | The customer terminated its subscription. Note that the termination will be effective at the end of the billing period. Meanwhile, they can cancel this termination.. |
| permission | The customer changed its registered payment method. |
| invoice | The customer paid a due invoice. |
| portal | The user was not redirected from a Customer Workflow but from the Customer Portal. See this article to know more. |
Values of the ‘outcome’ parameter
Section titled “Values of the ‘outcome’ parameter”This parameter indicates how the workflow ended.
| Value | Description |
|---|---|
| nocharge | The customer was not charged. Either the operation is free or the payment is due later. |
| paid | A payment was processed and complete. |
| pending | A payment was processed and is pending. |
| due | A payment is expected for a customer with an offline payment method. |
| registered | The customer registered its payment method, but no payment was processed. |
Use cases
Section titled “Use cases”The most standard use-case for this redirection is refreshing the user’s permission after a successful subscription-billing process. This is recommended in this article about rights management.
Another use case is to fluidify the customer experience by sending them directly to the right page of your application, avoiding a useless ‘payment success’.