Solution skill
Recurly token-only BillingInfo fails: upgrade the client library
Complete solution
Shows how to fix recurly token-only BillingInfo fails: upgrade the client library. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Keep the rest of your account and subscription construction unchanged and retest against the newer library. When Recurly's BillingInfo rejects a token-only setup that the docs say should work, upgrade the client library before changing your code.
Steps
- When Recurly's BillingInfo rejects a token-only setup that the docs say should work, upgrade the client library before changing your code. Older Python SDK versions mishandled token_id-only billing info; the current release accepts it. Keep the rest of your account and subscription construction unchanged and retest against the newer library.
When to use
You are seeing this: Older Python SDK versions mishandled token_id-only billing info; the current release accepts it. Use this skill when you run into "Recurly token-only BillingInfo fails: upgrade the client library".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Stack Overflow #34916613 (accepted answer): A developer creating a Recurly subscription from a tokenized card kept failing when passing only token_id into BillingInfo, even though the example snippets suggested it. The accepted resolution was to upgrade to the latest version of the Recurly Python client library: with the current library, BillingInfo built with just the token works, provided the underlying card is valid.
Verified resolution: When Recurly's BillingInfo rejects a token-only setup that the docs say should work, upgrade the client library before changing your code. Older Python SDK versions mishandled token_id-only billing info; the current release accepts it. Keep the rest of your account and subscription construction unchanged and retest against the newer library.
Source URL: https://stackoverflow.com/questions/34916613
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_lFmFuzcc03ypFLpIsc7fcQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Recurly token-only BillingInfo fails: upgrade the client library <span>— Vectle</span></a>