Hosted in France, on OVHcloud
Your application sends an email to a Facteur address, and your test reads the message with its verification code and its links already extracted. SMS are read the same way: the SMS page says how to ask for a number.
No card required. 500 messages a month, free, with no end date.
It receives real mail for one hour, ten messages at most. No account, no card, nothing to install.
Getting an address means you accept the terms of use and the limits they set on the trial.
Send an email to this address
Expires in
--:--
Messages
The name before the @ is yours: signup@, otp+42@, anything you like. They all land in the same place.
This address is not confidential: anyone can write to it, and whoever uses this browser during the hour reads what arrives. Never have a password reset link or a code for a real account sent here.
Built by the team that was testing electronic signature journeys, and paying the bill for it.
The whole signing journey: sending the document to the signer, a reminder on day two, a one-time code to authenticate, a signature receipt to both parties.
6,400 messages a day
The same journey runs in staging and, every five minutes, as a smoke test against production. If the code takes a minute to arrive, the signature fails for a real customer.
Account opening: address verification, one-time code by SMS, acknowledgement of supporting documents, a reminder on day two if the file is still incomplete.
4,200 messages a day
A code that fails to arrive in staging means a release pushed back by a week.
The full order lifecycle: confirmation, picking, dispatch, delivery, return and refund, in six languages and two currencies.
11,000 messages a day
A broken tracking link in the German version only shows up if you actually read the email.
Appointment reminders at seven days and one day out, consent capture, sending the report, patient cancellation straight from the SMS.
2,800 messages a day
The reminder must go out at the right hour, in the right timezone. One hour off and the patient does not turn up.
Claim handling: acknowledgement, request for a missing document, loss adjuster appointment, settlement notice carrying the amount and the payment date.
1,600 messages a day
The right amount, for the right policyholder, on the right claim. That gets read out of the message, not assumed.
Interview invitation, reminder the day before, a single-use video link, a nudge to the recruiter if the candidate has not replied.
5,500 messages a day
An interview link already burned by yesterday's test run, and the candidate is left outside.
Your test writes to an address of its inbox, then asks the API for the message. The answer comes with what Facteur has already extracted: the code in otp, the links in links. There is nothing left to parse.
An inbox is the box where the messages of one of your tests arrive. Facteur gives it an address that receives on a whole domain: everything before the at sign is yours.
Your application sends its email to that address, as it would to a customer. You change nothing in the application under test.
Your test searches for the message every second and reads it as soon as it arrives, with its code and links. The Playwright and Cypress plugins do it in one line.
La Belle Etoile is a demonstration shop. It sends real emails to a Facteur address: a confirmation code, an order number, a parcel tracking link, a PDF invoice. Next to each screen, it shows the few lines of the test that reads that message back through the Facteur API. Its code is public.
{
"messages": [
{
"id": "0198f0a0-7d3e-7000-8000-00000000e2a1",
"inbox": "ab12cd34",
"type": "email",
"status": "parsed",
"receivedAt": "2026-10-13T09:41:07+00:00",
"deliveryMs": 7,
"fromAddress": "no-reply@your-app.com",
"toAddress": "signup+run-42@ab12cd34.inbox.facteur.eu",
"subject": "Confirm your address",
"otp": "265279",
"codes": [
"265279"
],
"links": [
"https://your-app.com/v/8Kd2"
],
"attachments": []
}
],
"nextCursor": null
}
The API serves your tests; the interface serves the moment they fail. It is the same inbox opened in a browser, with what Facteur extracted marked in the message it came from.
Facteur takes the 4-to-8-digit number that follows a cue word (« code », « verification », « one-time ») and drops the rest. Nothing to configure for an ordinary message.
In the source of the message, every extracted value is marked. When an extraction gets it wrong, you can see at once what it landed on.
The time Facteur took to accept the message is shown for each one. It is the product's promise, so it is measured on screen rather than claimed on this page.
We validate electronic signature journeys: sending the document, chasing the signer, the one-time code, the signature receipt. In development first, then replayed continuously as a smoke test against production. Thousands of messages a day, and a requirement on delay. These four sentences are the ones we read in our own tool, and each has an answer in the product.
« Daily email limit exceeded. Your quota will reset in around 10 hours. »
One runaway test suite on a Tuesday morning, and the whole team is stopped until the evening. The only way out on offer: raise your subscription.
A volume pack adds to your plan without touching the subscription, and overage can take over up to the spending cap you set. Buying a pack online waits for card payment, which is not in service yet.
« Upgrade to the Enterprise plan to set custom usage limits per inbox. »
Without isolation, a single misbehaving inbox drains the quota of every other one. The feature exists; it is simply reserved for large contracts.
Per-inbox limits are included from the Solo plan, the first paid one. Daily or monthly limits, and you decide whether going over refuses messages or merely alerts you.
Doubling your capacity for a week means committing to the higher tier for the whole month, then waiting for the next cycle to come back down.
Volume is counted apart from the subscription. A pack stays valid for 12 months, stacks with the others and stays usable after a change of plan.
« Usage aggregated by date. »
You find out about the overage when CI breaks, and the dashboard will not tell you which inbox caused it.
Facteur writes to you at 80% and at 100% of the volume, and when the pace of the last days runs it out before the end of the period. Usage is broken down per inbox: the screen answers “who used up my quota”, not just “how much”.
Prepaid packs you burn at your own pace, overage billed at the end of the period if you would rather not plan ahead, and a spending cap so you never discover a bill.
See the pricingKeep CI apart from staging, team A apart from team B. Each inbox has its own limit and its own behaviour when exceeded, and a workspace can have one too.
Quotas and alertsA volume filling up is something you can see coming: at 80% and 100%, Facteur writes to the owners and administrators. You add your own thresholds. From the Solo plan, the alert also reaches Slack, Discord, PagerDuty or OpsGenie.
AlertsThe application and its database are hosted in France, at OVHcloud. The list of sub-processors and the data processing agreement are published on this site, without talking to sales. Retention follows your plan and deletion runs every hour.
SovereigntyThere is no compatibility layer: you replace the call that waits for the message, and your addresses can stay as they are. The migration guide lists the Facteur call for each task of a suite, and the four places where the shapes differ.
// Poll a shared mailbox until the email shows up
let email;
for (let attempt = 0; attempt < 10 && !email; attempt++) {
await sleep(3000);
email = await mailbox.latest({ to: 'signup@example.test' });
}
// The test's own address, searched every second
import { test, expect } from 'playwright-facteur';
test('signup', async ({ page, inbox }) => {
await page.fill('#email', inbox.address());
await expect(inbox).toReceiveEmail({ subject: 'code' });
const code = inbox.latest?.otp; // already extracted
});
An inbox receives for every address of its domain. Two tests running at the same time each have their own and never read each other's message.
Your test searches for the message every second and reads it as soon as it arrives. The Playwright and Cypress plugins do it for you: no fixed pause.
Facteur finds the one-time code of the message (4 to 8 digits) and puts it in a field. Your test reads that field instead of digging through the text.
HTML and text bodies, complete headers and what the SMTP connection saw. What arrived is what you read.
Name, size and SHA-256 checksum of every file, kept apart from embedded images such as a signature.
From the Solo plan, you ask for a phone number for an SMS inbox. That number has its own price, on top of the plan. The SMS page says what is open today.
The links of the message come back without the escape characters of HTML. Your test can open them as they are.
Only the messages you receive and keep count toward the number your plan includes. Reading a message forty times adds nothing.
SAML 2.0 and OIDC, one provider per organisation, with no quote-only plan in the way.
Chosen permissions, the workspaces a key reaches and an expiry date. A key is rotated or revoked from the application.
From 3 to 60 days depending on the plan, then Facteur deletes the message, its raw file and its attachments.
An HTTP API that asks for no dependency, described on the developer portal. The Playwright and Cypress plugins install from npm.
No. The trial page lends you a disposable address. It stays valid for one hour and receives ten messages at most. Send it an email and it shows on the page.
No. Every inbox receives on its own domain, and any address ending in it is accepted from the first message on. You derive one address per test (signup+42, signup+43) without calling the API to create it, and without deleting it afterwards.
You are told before it happens: Facteur writes to you at 80% and at 100% of the volume. Beyond that your packs are drawn down, then overage takes over within the spending cap you set. On the Free plan, further messages are refused until the next period. You can also put a limit on an inbox that refuses messages rather than billing them.
No, it has no end date and asks for no card. It includes 500 messages a month, enough to run a small test suite continuously, not to evaluate the product for two weeks before you have to pay.
As long as your plan says. After that, Facteur deletes the message, its raw file and its attachments. Deletion runs every hour and cannot be turned off.
Yes. You create an SMS inbox and ask the team for a number, from the Solo plan. Each number has its own price, on top of the plan, and the Free plan allows none. The SMS page says how.
The application and its database are hosted at OVHcloud. Raw messages and attachments are stored in the same place. The Sovereignty page details what is stored and who can read it.
The Free plan has no end date and asks for no card. If you come from another tool, the migration guide says what to replace in your suite.