Set billing provider configurations for a customer

Create a billing configuration for a customer. Once created, these configurations are available to associate to a contract and dictates which downstream system to collect payment in or send the invoice to. You can create multiple configurations per customer. The configuration formats are distinct for each downstream provider.

Use this endpoint to:

• Add the initial configuration to an existing customer. Once created, the billing configuration can then be associated to the customer’s contract.
• Add a new configuration to an existing customer. This might be used as part of an upgrade or downgrade workflow where the customer was previously billed through system A (e.g. Stripe) but will now be billed through system B (e.g. AWS). Once created, the new configuration can then be associated to the customer’s contract.

Delivery method options:

• direct_to_billing_provider: Use when Metronome should send invoices directly to the billing provider’s API (e.g., Stripe, NetSuite). This is the most common method for automated billing workflows.
• tackle: Use specifically for AWS Marketplace transactions that require Tackle’s co-selling platform for partner attribution and commission tracking.
• aws_sqs: Use when you want invoice data delivered to an AWS SQS queue for custom processing before sending to your billing system.
• aws_sns: Use when you want invoice notifications published to an AWS SNS topic for event-driven billing workflows.

Key response fields:

The id for the customer billing configuration. This id can be used to associate the billing configuration to a contract.

Usage guidelines:

Must use the delivery_method_id if you have multiple Stripe accounts connected to Metronome.