CbSubs question

Hello,

We are using CB Paid Subscriptions with the PayPal payment gateway and rely on the available substitution fields generated from PayPal IPN data.

For EU VAT compliance under the One-Stop Shop (OSS) rules for B2C digital services, we are required to determine the customer’s country of residence using objective evidence provided by the payment process.

PayPal provides a "residence country" value as part of the transaction data, which is relevant for VAT location determination. However, this field is currently not available as a substitution field that we can use in CBSubs.

We would like to know if the PayPal "residence_country" value can be made available as a standard substitution field, similar to other existing Payment substitutions ([INVOICE_ID], [INVOICE_NO], [PROFORMA_INVOICE_NO], [ITEMS_NAME]... etc).

This would allow us to retain and use this information as supporting evidence for OSS VAT compliance.

Thank you in advance for your help.

So the invoice address that the user supplies isn't sufficient? We already have [PAYER_EMAIL] substitution so it'd probably make sense to have [PAYER_COUNTRY] in this case.

Ok, added and implemented a feature ticket for exposing residence_country as [PAYER_COUNTRY]. I've also added [PAYER_NAME] as well.

forge.joomlapolis.com/issues/9812

Once reviewed and merged we'll release a new build with this implemented.

Thank you very much Krileon.
Just for context, this is not a requirement specific to our site. For EU-based companies selling B2C digital services (such as subscriptions to online content or SaaS), OSS VAT rules require determining the customer’s Member State using objective transaction evidence.
Because of this, access to a payer-derived country value from the payment provider is effectively a must-have for EU merchants.
Thanks again for your kind help.

Ok, this is now implemented in latest CBSubs build release. Anywhere you could use [PAYER_EMAIL] you can now also use [PAYER_NAME] and [PAYER_COUNTRY]. 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.

Thank you Krileon.