Hello again...
We updated to the latest CBSubs build that added the substitutions [PAYER_COUNTRY] and [PAYER_NAME].
In our payment confirmation emails (same place where [PAYER_EMAIL] substitutes correctly), [PAYER_COUNTRY] and [PAYER_NAME] return "[PAYER_COUNTRY]" and "[PAYER_NAME]", not the values sent in IPN, even though PayPal sends these values in the VERIFIED IPN payload for the same transactions.
Example (redacted) from raw IPN POST:
residence_country = GR
first_name = John Doe
last_name = Doe
payer_email = johndoe@gmail.com ([PAYER_EMAIL] substitutes this value correctly)
Since the PayPal IPN contains the data but the new substitution tokens do not substitute while other PayPal/basket substitutions work, is there a case that the new tokens may not be mapped to the stored transaction fields that the substitution engine is reading?
How we tested: CbSubs / Plan / Integrations / Email tab...
There, in the mail body field, we have...
Code:
<b>Subscription Details:</b><ul>
<li>Plan: [PLAN_ALIAS]</li> -> Substitutes correctly in the received mail.
<li>Total Price: [TOTAL_PRICE]</li> -> Substitutes correctly in the received mail.
<li>Account ID: [user_id]</li> -> Substitutes correctly in the received mail.
<li>Start Date: [SUBSCRIPTION_SIGNUP_DATE]</li> -> Substitutes correctly in the received mail.
<li>Item#: [ITEMS_NUMBERS]</li> -> Substitutes correctly in the received mail.
<li>Accessed: Digital Content and Services</li>
<li>Transaction ID: [TRANSACTION_ID]</li> -> Substitutes correctly in the received mail.
<li>Payment Method: [PAYMENT_METHOD]</li> -> Substitutes correctly in the received mail.
<li>Client PayPal Email: [PAYER_EMAIL]</li> -> Substitutes correctly in the received mail.
<li>PayPal user country: [PAYER_COUNTRY]</li> -> Returns "[PAYER_COUNTRY]" in the received mail.
<li>PayPal user name: [PAYER_NAME]</li> -> Returns "[PAYER_NAME]" in the received mail.
</ul>
So, according to your last reply...
Anywhere you could use [PAYER_EMAIL] you can now also use [PAYER_NAME] and [PAYER_COUNTRY].
Something seens not working fine.
We can't guarantee they'll have a value though as it's subjective to the payment processor giving that information back in their API calls or webhooks.
The values exist PayPal IPN!
Thank you.
