AI-generated Key Takeaways
-
This section details the payments account information linked to a billing setup.
-
Key fields include
payments_account_id
,payments_account_name
,payments_profile_id
,payments_profile_name
, andsecondary_payments_profile_id
. -
IDs (
payments_account_id
andpayments_profile_id
) are specific digit counts and require dashes when passed as strings. -
payments_account_name
is an immutable field used for naming the payments account for invoice reconciliation. -
secondary_payments_profile_id
is an output-only field used in uncommon scenarios like sequential liability agreements.
Container of payments account information for this billing.
Fields | |
---|---|
|
Output only. A 16 digit id used to identify the payments account associated with the billing setup. This must be passed as a string with dashes, for example, "1234-5678-9012-3456". |
|
Immutable. The name of the payments account associated with the billing setup. This enables the user to specify a meaningful name for a payments account to aid in reconciling monthly invoices. This name will be printed in the monthly invoices. |
|
Immutable. A 12 digit id used to identify the payments profile associated with the billing setup. This must be passed in as a string with dashes, for example, "1234-5678-9012". |
|
Output only. The name of the payments profile associated with the billing setup. |
|
Output only. A secondary payments profile id present in uncommon situations, for example, when a sequential liability agreement has been arranged. |