| Prio | Original string | Translation | — |
|---|---|---|---|
| All webhooks appear to be working correctly. | You have to log in to add a translation. | Details | |
| Some event types have not yet been triggered in Stripe. More information will be available here once Stripe attempts to send webhooks for each event type. In the meantime, please ensure that you have a webhook set up in Stripe for the Webhook URL shown below with all of the listed event types active. | You have to log in to add a translation. | Details | |
|
Some event types have not yet been triggered in Stripe. More information will be available here once Stripe attempts to send webhooks for each event type. In the meantime, please ensure that you have a webhook set up in Stripe for the Webhook URL shown below with all of the listed event types active.
You have to log in to edit this translation.
|
|||
| Some webhooks recently sent by Stripe have not been received by your website. Please ensure that you have a webhook set up in Stripe for the Webhook URL shown above with all of the listed event types active. To test an event type again, please resend the most recent webhook event of that type from the Stripe webhook settings page or wait for it to be sent again in the future. | You have to log in to add a translation. | Details | |
|
Some webhooks recently sent by Stripe have not been received by your website. Please ensure that you have a webhook set up in Stripe for the Webhook URL shown above with all of the listed event types active. To test an event type again, please resend the most recent webhook event of that type from the Stripe webhook settings page or wait for it to be sent again in the future.
You have to log in to edit this translation.
|
|||
| Webhook History | You have to log in to add a translation. | Details | |
| A webhook in Stripe is required to process payments, manage failed payments, and synchronize cancellations. | You have to log in to add a translation. | Details | |
|
A webhook in Stripe is required to process payments, manage failed payments, and synchronize cancellations.
You have to log in to edit this translation.
|
|||
| Your webhook is enabled. | You have to log in to add a translation. | Details | |
| Click here to connect via API settings. | You have to log in to add a translation. | Details | |
| Having trouble connecting through the button above or otherwise need to use your own API keys? | You have to log in to add a translation. | Details | |
|
Having trouble connecting through the button above or otherwise need to use your own API keys?
You have to log in to edit this translation.
|
|||
| Stripe API Settings | You have to log in to add a translation. | Details | |
| Admin: There was a problem processing a refund for transaction ID %1$s. Gateway Error: %2$s. | You have to log in to add a translation. | Details | |
|
Admin: There was a problem processing a refund for transaction ID %1$s. Gateway Error: %2$s.
You have to log in to edit this translation.
|
|||
| Admin: Order successfully refunded on %1$s for transaction ID %2$s by %3$s. | You have to log in to add a translation. | Details | |
|
Admin: Order successfully refunded on %1$s for transaction ID %2$s by %3$s.
You have to log in to edit this translation.
|
|||
| Subscription transaction ID is empty. | You have to log in to add a translation. | Details | |
| Something went wrong creating plan with PayPal; missing PROFILESTATUS. | You have to log in to add a translation. | Details | |
|
Something went wrong creating plan with PayPal; missing PROFILESTATUS.
You have to log in to edit this translation.
|
|||
| User: %1$s<br />Email: %2$s<br />Membership Level: %3$s<br />Order #: %4$s<br />Original Profile Start Date: %5$s<br />Adjusted Profile Start Date: %6$s<br />Trial Period: %7$s<br />Trial Frequency: %8$s<br /> | You have to log in to add a translation. | Details | |
|
User: %1$s<br />Email: %2$s<br />Membership Level: %3$s<br />Order #: %4$s<br />Original Profile Start Date: %5$s<br />Adjusted Profile Start Date: %6$s<br />Trial Period: %7$s<br />Trial Frequency: %8$s<br />
You have to log in to edit this translation.
|
|||
| There was a potential issue while setting the 'Profile Start Date' for a user's subscription at checkout. PayPal does not allow one to set a Profile Start Date further than 1 year out. Typically, this is not an issue, but sometimes a combination of custom code or add ons for PMPro (e.g. the Prorating or Auto-renewal Checkbox add ons) will try to set a Profile Start Date out past 1 year in order to respect an existing user's original expiration date before they checked out. The user's information is below. PMPro has allowed the checkout and simply restricted the Profile Start Date to 1 year out with a possible additional free Trial of up to 1 year. You should double check this information to determine if maybe the user has overpaid or otherwise needs to be addressed. If you get many of these emails, you should consider adjusting your custom code to avoid these situations. | You have to log in to add a translation. | Details | |
|
There was a potential issue while setting the 'Profile Start Date' for a user's subscription at checkout. PayPal does not allow one to set a Profile Start Date further than 1 year out. Typically, this is not an issue, but sometimes a combination of custom code or add ons for PMPro (e.g. the Prorating or Auto-renewal Checkbox add ons) will try to set a Profile Start Date out past 1 year in order to respect an existing user's original expiration date before they checked out. The user's information is below. PMPro has allowed the checkout and simply restricted the Profile Start Date to 1 year out with a possible additional free Trial of up to 1 year. You should double check this information to determine if maybe the user has overpaid or otherwise needs to be addressed. If you get many of these emails, you should consider adjusting your custom code to avoid these situations.
You have to log in to edit this translation.
|
|||
Export as