Hi Joan,
Yes you are probably right about PayPal tokens not needing to be mapped to core DNN. I know what you are looking to see is some kind of token list in the completion event area for email that have the values of these listed below from paypal:
subscr_date: $(PayPal:subscr_date)
txn_id: $(PayPal:txn_id)
txn_type: $(PayPal:txn_type)
subscr_id: $(PayPal:subscr_id)
p1: $(PayPal:period1)
If paypal is passing them back so that your Dynamic registration page can receive them then Try making some hidden fields with short names that are equal to the names of the tokens in paypal but don't map them to dnn. Each hidden field will then also have an area in Advanced Field options where you can check a box to:
'Retrieve values from querystring variable' or
'Retrieve values from session variable' or
'Retrieve values from cookie variable' for this question: For an experiment it wouldn't matter if all these boxes are checked.
Then if you go to the completion event area where your email is set up you should see tokens there with the names of the paypal tokens. The trick is do they receive the values from paypal so that when you put them in your email body the email shows real values when you send it to yourself.
If this quick idea doesn't work then for now you will need to google; site
ataSprings paypal for some forum threads on our site that might have some more info because something is still missing.
If you draw a blank on all this then get back to us with a question in the following area as that will put a different set of eyes on the problem:
http://datasprings.com/contact-us
Thanks