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.

Context: 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.

## Matched source
Source: Published skill
Original query: "Recurly token-only BillingInfo fails: upgrade the client library"
Key terms: billinginfo, client, fails, library, only, recurly, token, upgrade