Frequently asked questions

Peppost takes invoices and credit notes you have already issued in Stripe and delivers them to the recipient over the Peppol network. We generate the compliant UBL document, attach the original Stripe PDF, and dispatch it through a certified access point.

Stripe-billing businesses whose customers, government bodies, or procurement platforms require Peppol delivery. It is aimed at consultants, agencies, B2B SaaS, finance ops teams, and service businesses that do not want to migrate their billing to a heavier ERP just to satisfy that requirement.

No. Stripe stays the system of record for invoicing, customers, and payments. Peppost only adds the Peppol delivery layer on top of what is already in Stripe.

Peppol (Pan-European Public Procurement Online) is a network for exchanging structured electronic business documents. It is mandated for public-sector invoicing across most of the EU and is increasingly required for B2B invoicing in countries such as Belgium, France, Poland, and Germany.

UBL 2.1 invoices and credit notes following the Peppol BIS Billing 3.0 profile, compliant with the European e-invoicing standard EN 16931. The original Stripe PDF is attached as a human-readable rendering inside the same document.

Peppol works EU-wide and in several additional jurisdictions (Norway, Singapore, Australia, New Zealand, Japan, and others). If the recipient has a Peppol participant ID, you can send to them.

When you start a send in Peppost, we look up the recipient against the Peppol directory using their VAT or company identifier. If they are registered and accept invoices, the send goes through. If they are not, we tell you before any credit is consumed.

Click Sign in with Stripe on any page. Stripe Connect handles the OAuth step, and we pre-fill your company profile (legal name, VAT number, address, country) from the details Stripe already has. Onboarding takes under five minutes.

No. As part of onboarding we register your account on the Peppol network through our certified access point provider. You do not need to deal with access points, SMP records, or participant identifiers directly.

Yes. Test-mode Stripe accounts work end to end inside Peppost so you can rehearse the flow. Real Peppol delivery only happens for live-mode invoices; test-mode invoices use a sandbox path that does not reach external recipients.

Open Settings in the app and revoke the Stripe Connect link. You can also revoke access from your Stripe dashboard under Connected applications. Either path stops Peppost from accessing the account.

Finalised Stripe invoices and Stripe credit notes. Drafts are excluded because their numbering and totals are not yet authoritative.

The Invoices screen lists everything available from Stripe with their Peppol delivery status. You pick a row, confirm the recipient lookup, and dispatch.

Most sends reach the recipient's access point within seconds. Final delivery confirmation depends on the recipient's system and is usually reported back within a few minutes.

Once a document has entered the Peppol network it cannot be recalled — that is a property of the network, not Peppost. If a document needs to be corrected, the right answer is to issue a Stripe credit note and a new invoice, both of which can be sent through Peppost.

You see the failure on the dashboard and the credit is refunded automatically when the failure happens before the document leaves our access point. Errors raised by the recipient's access point after delivery are reported with the original network error message.

New accounts start with 3 free credits, so the first 3 sends are on us. After that, credit packs start at €10 for 100 credits and drop to €0.07 per send on the largest pack. Full breakdown on the pricing page.

No. Peppost is pay-per-send via prepaid credit packs.

No. Credits remain on the account until you spend them.

Each credit purchase generates a Stripe receipt with VAT breakdown. You can download it from the Credits page, in the transaction history, right next to the matching purchase line.

Account data, send history, and credit ledger are stored in a Postgres database hosted in the EU. Document payloads are relayed to the access point at send time and not retained as long-term archives.

For your own account data Peppost is the controller. For the invoice content you transmit to your customers, you are the controller and Peppost is the processor. Details are in the privacy policy.

No. Stripe Connect issues a scoped OAuth credential. We never see your Stripe API secret keys.

Yes. Email legal@peppo.st and we will send a signable copy.

Email support@peppo.st with the relevant invoice number or Peppost transaction ID. We aim to reply within one business day.

The full guide lives at /docs.