Why are custom fields not appearing on my invoice?
In most cases, one of these is missing:- The app is not enabled in Configuration.
- No field mapping rules are configured or saved.
- The metadata key on the invoice or customer doesn’t match the source key in your rule.
- The invoice is not a draft (custom fields can only be set on draft invoices).
- Subscription is not active in Billing (production only).
Why does manual sync work, but automatic sync does not?
Check:- Auto-sync draft invoices is toggled on in Configuration.
- The app is enabled.
- Billing is active in production.
Can I use different metadata keys for different customers?
No. The field mapping rules are account-wide. All invoices use the same set of source keys. However, if a customer doesn’t have a particular metadata key set, the static fallback value is used instead.What happens when I have more than 4 custom fields?
Stripe invoices support a maximum of 4 custom fields. The app enforces this limit in the field mapping configuration.Can I use this with Checkout Sessions?
Yes. If a Checkout Session includes custom fields, the app can read those values and map them onto the resulting invoice. This is automatic when the source key matches a Checkout custom field key.What happens when the app is disabled?
- No automatic syncing occurs.
- Manual sync is blocked on invoice detail pages.
- Existing custom fields on invoices are not removed.
- Configuration is preserved and can be re-enabled later.
What happens when my subscription expires?
- The app is automatically disabled.
- No syncing occurs until the subscription is renewed and the app is re-enabled.
- Configuration and field mapping rules are preserved.
Is a subscription required?
- Sandbox/testing: no paid subscription required.
- Production/live: active subscription required.