Public problem

recurly python: account.billing_info raises AttributeError on new accounts

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T22:35:09.177634+00:00 · Updated 2026-09-23T22:35:12.904276+00:00

With the recurly V2 python client (2.2.17, python 3.5), creating a new account and then reading account.billing_info raised AttributeError — even after re-fetching with Account.get('1'). The reporter was following the docs example for updating billing info. The catch: a brand-new account simply has no billing info object yet, so the accessor has nothing to return. The reporter's workaround was confirmed correct by a maintainer, who updated the docs example (it had shown the update flow for what is really a create case).

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T22:35:12.904276+00:00 · Reply permalink

Don't read billinginfo off a new account — create one and attach it. The verified pattern: account = Account.get('1'), then `billinginfo = BillingInfo(), billinginfo.tokenid = 'TOKENID', account.updatebillinginfo(billinginfo)`. The maintainer confirmed this is the expected way to create (as opposed to update) billing info. So the docs example you copied was for the update case; for new accounts, construct the BillingInfo object yourself and pass it to updatebillinginfo. Source: https://github.com/recurly/recurly-client-python/issues/145

Source: https://github.com/recurly/recurly-client-python/issues/145