| Prio | Original string | 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.
|
|||
| Payflow does not use IPN. To sync recurring subscriptions, please see the <a target="_blank" href="%s" title="the Payflow Recurring Orders Add On">Payflow Recurring Orders Add On</a>. | You have to log in to add a translation. | Details | |
|
Payflow does not use IPN. To sync recurring subscriptions, please see the <a target="_blank" href="%s" title="the Payflow Recurring Orders Add On">Payflow Recurring Orders Add On</a>.
You have to log in to edit this translation.
|
|||
| Smart Authorization failed. | You have to log in to add a translation. | Details | |
| Apartment number missing or not found. Check that your billing address is valid. | You have to log in to add a translation. | Details | |
|
Apartment number missing or not found. Check that your billing address is valid.
You have to log in to edit this translation.
|
|||
| Error: The request was received, but there was a timeout at the payment processor. | You have to log in to add a translation. | Details | |
|
Error: The request was received, but there was a timeout at the payment processor.
You have to log in to edit this translation.
|
|||
| The capture or credit is not voidable because the capture or credit information has already been submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided. | You have to log in to add a translation. | Details | |
|
The capture or credit is not voidable because the capture or credit information has already been submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided.
You have to log in to edit this translation.
|
|||
| The request ID is invalid. | You have to log in to add a translation. | Details | |
| The referenced request id is invalid for all follow-on transactions. | You have to log in to add a translation. | Details | |
|
The referenced request id is invalid for all follow-on transactions.
You have to log in to edit this translation.
|
|||
| The authorization has already been captured. | You have to log in to add a translation. | Details | |
| The authorization has already been reversed. | You have to log in to add a translation. | Details | |
| The customer matched an entry on the processors negative file. | You have to log in to add a translation. | Details | |
|
The customer matched an entry on the processors negative file.
You have to log in to edit this translation.
|
|||
| The card has reached the credit limit. | You have to log in to add a translation. | Details | |
| American Express Card Identification Digits (CID) did not match. | You have to log in to add a translation. | Details | |
|
American Express Card Identification Digits (CID) did not match.
You have to log in to edit this translation.
|
|||
| Error: The request was received, but a service did not finish running in time. | You have to log in to add a translation. | Details | |
|
Error: The request was received, but a service did not finish running in time.
You have to log in to edit this translation.
|
|||
Export as
