Sending customer details from Stripe
Quaderno reads customer details directly from Stripe to populate your invoices and credit notes. This article lists which Stripe fields Quaderno reads and the order it falls back to when a field is missing.
This reference is aimed at integrators and developers. If customer details are missing from your documents, contact your third-party platform's support team — they control what data is sent to Stripe.
| Basic data | Stripe sources, in fallback order |
|---|---|
| Customer's name | 1. Customer name
2. Shipping name 3. Cardholder name 4. Customer description |
| Customer's billing address | 1. Shipping address
2. Customer billing address 3. Card billing address |
| Customer's tax ID | 1. Customer tax ID object
2. Customer metadata field: tax_id or business_number
3. Charge metadata field: tax_id |
| Customer's IP address | 1. Charge metadata field: ip_address
2. Customer metadata field: ip_address |
When a tax ID is removed from a Stripe customer, Quaderno removes it too. If the Stripe customer has another tax ID that matches their country, Quaderno assigns that one instead.
Extra metadata for charges and subscriptions
Quaderno reads the following fields from the metadata object on Stripe charges and subscriptions:
| Metadata field | Description |
|---|---|
transaction_type |
Type of transaction: eservice, ebook, saas, standard, reduced, exempt, consulting. Defaults to the type set on your preferences page. |
sku |
Unique product code. Useful for tracking sales across multiple platforms. |
tax_name |
Tax name, e.g. Sales Tax, VAT, GST. |
tax_rate |
Tax rate value, e.g. 20 for 20%. |
ip_address |
Customer's IP address. |
po_number |
Purchase order number. |
notes |
Note to add to the document. |
tags |
Comma-separated tags, e.g. tag1, tag2, tag3. |
contact_person |
Billing contact person (businesses only). |
email |
Email address to send the invoice to, if different from your Quaderno billing email. |