Paypal is stating certain transactions are being rejected due to security risk of not capturing client's address for AVS verification. I see no place in the gateway settings for Paypal Pro to turn on the address field.

In authorize.net, there is a simple field to turn it on. How do I do it for Paypal Pro so I can capture address? Even the generic Paypal Pro has a field for asking for client's shipping address (which really should have an option for billing address since they can be different).

Do you mean cbsubs\settings\DISPLAY TAB\baskets?

I've checked every tab under settings and don't see anything about including address. Can you please be more specific what I'm looking for?
Thank you!

Thank you for the details. I've turned that on and will see if that solves the issue. Is there a reason though you don't add the ability to turn on address fields in the Paypal Pro Gateway like it can be turned on in other gateways? That would seem to be make sense and avoid AVS issues with Paypal Pro.

In my testing, I see that by default it pulls the user's name from their community builder user name field. If they use a nickname at signup instead of their proper name (like shown on their credit card), they have to modify the invoice address details. Then when they choose to check out using Paypal Pro gateway for credit cards, the name field there again shows the nickname requiring them to once again change it. It is not good practice to require the client to go through multiple screens to attempt a checkout. You really need to add the address fields directly to the checkout box. When can you get this patched to do so? There is no reason at all to not have it since most processors require at least some type of AVS. Your decision to drop Authorize.net recurring billing updates is one thing but now using Paypal Pro (one of your recommended processors) is creating unnecessary headaches. Please tell me you plan to add the address option to Paypal Pro very soon. It's the correct solution to making Paypal Pro work correctly without requiring the use of a workaround. Keeping my fingers crossed!