Migrating Billing Features from the AdWords API to the Google Ads API

This guide compares the billing terms used in both APIs:

AdWords API	Google Ads API
Billing account	Payments account
Billing customer	Payments profile
Budget order	Account budget
n/a	Billing setup

Billing account (AdWords API) vs. Payments account (Google Ads API)

Both represent the same thing and each is indexed by a 16-digit ID (e.g., 1234-5678-9012-3456). This ID is needed to create a new billing setup in the Google Ads API.

• In the AdWords API, you use BudgetOrderService to get available billing accounts using getBillingAccounts.

• In the Google Ads API, you can retrieve this entity directly using PaymentsAccountService.ListPaymentsAccounts, which will return all available Payments accounts for your authenticated Google Ads account. You can also create a new Payments account at the same time you create a billing setup.

Billing customer (AdWords API) vs. Payments profile (Google Ads API)

Both represent the same thing and each is indexed by a 12-digit ID (e.g., 1234-5678-9012).

• The AdWords API doesn't allow you to manipulate this entity directly, but it appears as a part of BudgetOrder.

• You need this ID to create a new Payments account in the Google Ads API.

Budget order (AdWords API) vs. Account budget (Google Ads API)

Both represent the same thing and each is indexed by an ID.

• In the AdWords API, you use the BudgetOrderService to create a new BudgetOrder. Read more about budget orders.

• In the Google Ads API, you manipulate an AccountBudget via the AccountBudgetProposal. Read more about mutating account budgets.

Billing setup (Google Ads API)

• The AdWords API doesn't allow you to manipulate this entity directly.

• A billing setup is a link between a Google Ads account and a Payments account. This entity is needed for creating a new account budget in the Google Ads API.