I've run into a problem trying to use the Smart Payment Button integration. When I try to include "subscriber:" info (e.g. email or surname) with the other data submitted with actions.subscription.create(), it seems to get filtered out. The examples in the docs all seem to call subscription.create() with only plan_id and no other data, but it clearly says you can also pass other data as needed. It just doesn't say what data. I had assumed it would be exactly the same data as documented under the /v1/billing/subscriptions API call, but that doesn't seem to be true. To clarify, I can create a JSON object with the required fields such as product_id, plus an optional subscriber field with a name or email. If I then use this JSON object directly in an API call to /v1/billing/subscriptions, everything works as expected (by which I mean if I then check the details of the resulting subscription id, I will see the subscriber info as part of the record). But if instead of calling the API directly, I use exactly the same JSON object through the javascript interface by calling actions.subscription.create(), the subscription is created just fine but it does NOT contain the subscriber data I sent. So it seems the javascript interface for Smart Payment Buttons is only allowing some subset of fields, but I don't know which ones I can use. I really need to be able to send some extra identifying info along with the request, whether it's in the subscriber object or somewhere else. At this point it looks like it will be impossible for me to do unless I revert to using the API directly which I would rather not have to do. If anyone knows a way I can get this to work with the Smart Button interface, please let me know!
... View more
