The customer pays FIZ
After FIZ approves your Production app, the customer connects a company with an API-enabled plan and pays FIZ directly for that plan. You continue to bill for your own product separately.
Start integrating →FIZ for platforms
Portuguese invoicing, inside your product.
Your customer works in your app. FIZ provides invoicing through an authorized connection to their company. Understand the customer journey, who pays and where FIZ fits in.
For marketplaces, SaaS, booking platforms and business software.
Real interfaces with demo data. The example app is shown in English. Select an image for a closer look.
Your product. Your customer’s FIZ account.
The integration connects each company separately. In a marketplace, each seller can connect their company and issue their own documents while using the same platform.
-
1. Your product
You control the experience: orders, bookings, payments and when to request a document. Your app keeps its own name and interface.
-
2. Your customer
Signs in or creates a FIZ account, sets up their company, can connect AT and authorizes your app. Then returns to your product. AT credentials are entered in FIZ.
-
3. FIZ
Provides the invoicing API, documents and AT reporting. Issuance requires the company’s permissions, commercial access and fiscal setup to be valid.
Back to the order. With FIZ connected.
The app turns the order into a draft in the customer’s chosen company. The example shows the result inside your product; the document remains unissued.
View the example on GitHub →
Who pays for what?
OAuth provides the technical connection. The commercial model determines how customers get access. Here is what you can use now and what still needs agreement or development.
The platform pays FIZ
Want to include invoicing in your subscription? This model needs further development: partner-funded access and consolidated billing are not yet available. Contact FIZ with your expected volumes to discuss feasibility and commercial terms.
Discuss a pilot →Sell your app through FIZ
App registration and OAuth are available. A public App Store catalogue, app subscriptions collected by FIZ and developer payouts have not launched. Tell us if this model matters for your product.
Tell us your use case →White-label & embedded invoicing
Where your brand appears — and where FIZ appears
You can embed invoicing in your own product. The customer still has a FIZ account and sees FIZ during registration, AT connection and access authorization.
- Your app
- Your product’s name, domain, interface and commercial relationship remain yours. You decide how invoicing fits into your customers’ workflow.
- The account and fiscal connection
- The customer sets up their company and enters AT credentials in FIZ. Your app receives authorized API access, not the AT password.
- Customer control
- The customer chooses the company and permissions and can disconnect the app in Settings → Integrations. Disconnecting access does not delete their FIZ account or documents.
Full white-label — a custom FIZ domain, hiding FIZ entirely or removing the customer’s FIZ account — is not part of the current offering.
Common questions
Does the customer need to know about FIZ?
Yes. They use or create a FIZ account, set up their company and authorize your app. They can then keep working in your product. Other FIZ services depend on the plan they choose.
Can I connect multiple companies?
Yes, with separate authorization for each company. A token only accesses its authorized company. By default, an app reads the records it created; reading other records requires an additional permission approved by the customer.
How can I try it?
Register a Development app and run the guide’s Node.js example. It connects to live FIZ for you and listed testers, including new accounts. Data is real; the example saves a draft without issuing documents. Other customers need a FIZ-approved Production app.
Do I earn a commission for bringing customers?
Registering an app does not activate commissions. If you want a referral partnership, contact us to agree separate terms. OAuth does not include an automatic commission rate or payouts.
Let’s find the model for your product
Tell us what you are building, who issues the documents, how many companies you expect to connect and approximate monthly volume. Let us know who you want to pay for invoicing.
AT № 3041
NIPC 517696835
1200-082, Lisbon, Cais do Tojo 24