The issue tracker says that the payment_method_id is listed as a known issue that was fixed on January 22nd. However, it’s still not fixed.
/v2/subscriptions
payment_method_id property is present, but incorrectly populated as 0.
The property should be populated with the correct value.
/v2/subscriptions/{$id}
payment_method_id property is present and populated.
/v1/subscriptions/
Works properly but uses the old XMLRPC credit card ID’s instead of the REST v2 payment_method_ids.
This makes the data incompatible with other data from the v2 API.
Request #1:
Check the /v/2/subscriptions endpoint to make sure it matches the. behavior on the /v2/subscriptions/{$id} endpoint
Request #2:
Use the specific endpoint(s) in the tracker instead of just the general resource.
PS:
I don’t know if it’s intentional, but the /v/2/subscriptions and /v/2/subscriptions/{$id} don’t return the same fields. Only the single record retrieval pulls the shipping address. That section is missing altogether from the list subscriptions endpoint.