Several accounts on record, a single one ringed: on Vestiaire every gesture goes out from the account named on screen — never from “the first one available”.
Where your accounts live — two doors, two jobs
They are the same accounts, seen from two places, and each place does something the other does not.
The Vestiaire screen’s header also carries a counter — “
{n} usable account” — and the status line under the title ends with it. It is the number to read before a hunting session: a radar with zero usable accounts detects perfectly and can act on nothing.
Connecting an account
Adding and connecting are one gesture, not two. Our servers try the connection first and only write the account down if it opens. Nothing is saved from a refused attempt. The two doors do not word the fields the same way, and they do not offer the same ones:
The server asks for an address and at least one secret. With no address: “Enter the address of the Vestiaire account.” With neither password nor code: “Give this account’s password, or paste an existing session.”
While it runs, the button reads “CONNECTING…”. On success: “Account added and connected —
{name}”. On a refusal, the window stays open with the reason, and the field at fault is marked — the address, or the password. You correct and try again without retyping everything.
A pasted code is checked on a buying page, not on a harmless one. It would be easy to declare a session valid because it can read a listing; that proves nothing about paying. See “A connection can be whole for browsing and refused for buying” below — the whole product is built around that measurement.
The dedicated address, and why there are only twenty
Every Vestiaire account holds a dedicated address for its whole life — not a postal address: the route it uses to reach the marketplace. It is allocated when the account is connected and released when the account is deleted.An account that buys never borrows an address from the monitoring pool. The radar’s addresses are shared by every client at once; a buying account’s is its own, and it is not interchangeable. There is no fallback: with no dedicated address, the connection simply does not go out.These addresses are a finite stock — twenty of that grade — which is why the refusal below exists at all, and why deleting an account you no longer use is a real gesture and not housekeeping.
What can refuse an addition
Every one of these leaves your list exactly as it was.What rega keeps, and what it refuses to keep
Vestiaire serves us a great deal about the holder of an account. We refuse to carry most of it: the postal address, the postcode, the date of birth and the holder’s own e-mail address are among the details the marketplace hands over and that rega does not transport. What is kept is what a buying tool needs to show you and nothing else.
An account is always displayed under its Vestiaire username, failing that under its address — never under a technical identifier.
Reading an account’s state
The state is decided in a fixed order, and the first line that is true wins. That order matters: it is why an account you have set aside never shows as “Signed out”, and why “password to be saved” never hides behind a milder message.“Connected — to be renewed soon” asks nothing of you. The account will buy this evening exactly as it bought this morning. Usable and expiring are two different things: an account whose code runs out in two days is expiring and perfectly usable. Treating them as one would cut your buying off three days early.The reverse case is treated the other way round: an account whose end date cannot be read is assumed to be expiring. When in doubt we warn rather than reassure.
The full line concatenates, in this order: the address · “can buy” or “cannot buy” · the expiry, then, when they apply, “to reconnect soon” and “no password on record”. Read left to right, it answers the only three questions worth asking about an account before a session.
The five points that decide whether an account can buy
The account page carries a health strip. It is five points and an AND — never a score. Four points out of five green would read “almost ready” while the purchase fails; there is no such thing as almost. Each point holds one of three labels — “Ready”, “To watch”, “Missing”. A point that is not green also carries a “Fix →” button, which scrolls the page to the section where the gesture is made; a point at “Ready” carries none, because there is nothing to go and fix.The order of the points is the order in which you unblock them, and that is not decoration: a card is worth nothing without a connection, and a pick-up point makes no sense without a delivery method.Connection → Delivery address → Saved card → Delivery method → Pick-up point.
{n} points need watching.”, “One thing is missing: {what}.”, “{n} things are missing.”, or “Run a check to find out what is missing.”
Three behaviours of that strip are worth knowing, because each of them looked like a bug before it was measured:
The card point reads the cards saved on the account — not the payment methods of the basket
The card point reads the cards saved on the account — not the payment methods of the basket
Those two lists are not the same one. With a full basket, a perfectly equipped account offers three payment methods; with an empty basket, the same account offers none at all. Reading the second list would declare a healthy account cardless every time its basket happens to be empty.
An expired card is still listed as new by the marketplace
An expired card is still listed as new by the marketplace
Vestiaire keeps serving it with a healthy status. The expiry is therefore worked out here, from the date on the card, rather than taken on trust. It is not the only point where we set the marketplace’s own answer aside: the delivery address is another — Vestiaire marks a different address as the chosen one depending on where you ask it, so we read the delivery role carried by the address instead.
With PayPal, the card point reads “Not applicable”
With PayPal, the card point reads “Not applicable”
If the account’s payment family is PayPal, demanding a card would manufacture a shortage that does not exist. “Not applicable” is a green light of its own kind, not a gap.
A connection can be whole for browsing and refused for buying
A ring open over a third of its circumference: that is exactly what a half-valid Vestiaire connection looks like — whole where you look, broken where you pay.
- An account with a brand-new code shows “Not checked”, never “Connected”. The only green we accept on the connection point is one obtained by probing a buying page.
- The “Check” button exists for exactly this. It probes a page of the sensitive family — the least intrusive of them: it reads nothing of your basket and writes nothing.
- Its verdicts: on success, “Connected — this account can buy.”; on failure, “This account cannot buy.
{detail}”, falling back to “Reconnect it, then try again.” The reason served by our servers is: “the session is refused on the buying routes — it may still work elsewhere: it needs reconnecting”. - The button is greyed out while the account has no code at all, with the help “This account is not connected — connect it first”.
A check costs one round trip to the marketplace, so it is a gesture, not a background habit. It does not replace the free forecast you already read on the status line — it answers a different question. The expiry tells you when the connection ends; the check tells you whether it works for paying, today.
Thirty days, and what renews them
Reconnecting by hand answers with the same arithmetic: “Connected. The connection is to be renewed in 30 days.” A refusal reads “Connection refused.
{detail}”, with the fallback “Check the password, then try again.”
Two behaviours protect the account itself:
- Refused credentials are never replayed. If a renewal comes back with the password rejected, the account is set aside on the spot and you are told: “credentials refused — password changed, or account closed. The account is disabled: fix it to switch it back on.” Retrying a wrong password every hour is how accounts get locked.
- Anything that is not a refusal is retried on the next pass, and only reported when the end date is approaching: “session expiring soon and the renewal is failing (
{detail}).”
The maintenance pass runs on our servers, independently of the radar. It does not matter whether your radar is armed, or whether your browser is open. That was not always true, and an unarmed service used to renew nothing at all.
What Vestiaire tells us about the account
The account page carries a panel titled “MY VESTIAIRE ACCOUNT”. Before it is read, it announces what it will contain: “What Vestiaire knows about this account: purchases, sales, followers, how long it has been a member, and the welcome voucher if there is one.” It arrives in a single read: username, first and last name, profile sentence, photo, country, sign-up date, level, kind of account, badges, purchases, sales, items on sale, wished for, followers, following, items liked, buyer standing, seller standing, and whether the account is on hold.A missing counter is never shown as “0”. “No sales” and “we were not told” are two different facts, and only one of them is about the account. Everywhere in rega, an absent figure stays absent.
The welcome voucher
The panel shows it under “Your welcome voucher”. When there is none, it says so as a result rather than as a fault: “No welcome voucher on this account at the moment.”The amounts are copied exactly as Vestiaire writes them — “100 €”, “10 %”. The marketplace also serves a numeric field alongside them, and that field is worth
1 in both cases: it means nothing, so it is never used. Reformatting a voucher would be inventing a value.The four details you can correct
Exactly four, and the page says why: “These four details are the ones Vestiaire lets you change. The rest — country, sign-up date, statistics — belongs to it and is changed on its site.”1
Fill in the display name
It cannot be emptied, and the refusal comes before anything is sent: “Choose the name you appear under on Vestiaire: it cannot be left empty.”
2
Adjust the first name, the last name, the profile sentence
Those three may be left as they are.
3
Send, and read what we claim
The marketplace answers without a body — it says nothing about what it stored. So rega says what it knows and nothing more: “Your details have been sent to Vestiaire.” It does not pretend to have read them back.
What an account carries: the three gestures
Every gesture on a Vestiaire listing goes out from the account named on screen — under “From” in the item panel, and in the offer window. With a single account, its name is written out anyway, followed by “the offer will go out from this account”. That is deliberate: without a name on screen, our servers would take the first usable account, and your offer would be filed under an account nobody chose.A favourite
“Add to Vestiaire favourites” from a card’s menu, “Add to favourites” from an item panel. Once set, the button reads “In your favourites”.
An offer
One click, from the named account. With no usable account: “No Vestiaire account can make an offer”, subtitled “sort this out in Accounts”.
A purchase
Prepared from that account’s basket, paid after your bank confirms. The account is held for the whole of it.
A heart cannot be taken back from rega. The tooltip says it before you click: “Hearts the listing from your Vestiaire account. No effect if it was already there, and it cannot be removed from rega.” The button label never flips to “remove”, because the marketplace never tells us whether the heart was already there — and a button that fails silently is worse than an absent one.If the gesture fails, you read: “This item could not be added to favourites.”
One basket for the whole account
On Vestiaire the basket does not belong to a listing, it belongs to the account. Everything that follows comes from that one fact. A payment left waiting keeps holding the account. A banner brings it back to you, on the dashboard and on the Vestiaire screen, with its amount — titled “Your bank is waiting for your confirmation”, or “A Vestiaire payment is under way” when it is the marketplace that has not answered. Underneath, the reason: “While this payment waits, no other Vestiaire purchase can go out: the basket is shared across the account.” It refreshes every 20 seconds, and costs nothing while nothing is waiting. Two buttons: “Resume”, and “Cancel payment”, whose tooltip states both halves of what it does: “Closes this payment and empties the Vestiaire basket, so the account can buy again. The item will no longer be reserved for you.”This is not a theoretical problem. It happened on a real account: a payment sat waiting on its bank step — a €97 dress, €116.52 in the basket — because a bank confirmation had been interrupted two hours earlier. That single stuck line stopped the account from opening any other Vestiaire payment and stopped its pick-up point map from opening, because both need the same basket. There was no way out of it from the product; there is one now.
- “This account is already preparing a purchase. Finish it before opening the pickup-point map — both share the same basket.”
- “Your Vestiaire basket already holds an item. Empty it to display pickup points: the map needs the basket, and we will not discard your choice.”
The card, and the two ways of holding it
An account with no card detects and cannot buy: “Until a card is on record, this account detects items but cannot buy anything.” The card itself is registered with Vestiaire at the first purchase: “A card is saved with Vestiaire at the first purchase: rega presents it at payment, then Vestiaire keeps it and shows it here.” From then on the marketplace only asks for its security code at each purchase — and that is what the lighter of the two ways keeps, and only that: “rega keeps this card’s security code, and nothing else: the number stays with Vestiaire. That is all it takes to pay.” The heavier way keeps the whole card, number and security code alike, both encrypted, and the panel says so under the heading “CARD KEPT BY REGA”: “rega keeps this card for this account’s purchases.” Which of the two is open to you is decided for the whole installation, not on this screen — where it is closed you read “On this installation, rega keeps nothing in advance: the card is entered at purchase time.”Entrusting the security code is what lets the account prepare a purchase on its own — basket, delivery, card — leaving you the single step your bank asks for. It does not make the purchase happen without you: on the card we measured, the bank asked for its confirmation four times out of four. That demand comes from the card’s issuer, not from the marketplace — another card may well be exempt.
Deleting an account
The confirmation is short — Delete the account “{name}”? — and what happens behind it is not.
1
The dedicated address goes back to the pool first
Before anything is removed: afterwards there would be no account line left to match it to. Skipped, that address would leave the pool for good — out of twenty.
2
Then the card vault of that account is erased
Whatever it held for that account, security code included. It happens before the account line goes, because afterwards there would be nothing left to match those secrets to — and a secret nobody can reach any more is the worst kind.
3
The account line is removed
And if the address could not be handed back, the answer says so instead of keeping quiet. The deletion still stands; you simply know one address needs sorting out.
Our advice
1 · Save the password, never just a code
1 · Save the password, never just a code
A code alone lasts 30 days and nothing renews it. Our servers can only reconnect an account that has a password on record, and they do it on their own, every 7 days, without waiting for the expiry.The move: the sign-in code field is there for people who already hold one. In every other case, type the password.
2 · Click “Check” before a hunting session
2 · Click “Check” before a hunting session
A connection can be whole for browsing and refused for buying — measured on a real connection of ours. The “can buy” label in the list is not necessarily recent; the check is.The move: on the account you are about to hunt with, click “Check” and insist on “Connected — this account can buy.”
3 · Read the five points top to bottom, not as a score
3 · Read the five points top to bottom, not as a score
They are an AND. Four out of five is not “almost ready”, it is an account that will fail mid-race on an item the radar had found for you.The move: unblock them in the order they are printed — connection, address, card, delivery method, pick-up point. Each one carries the gesture and the “Fix →” that takes you there.
4 · Name your accounts as you add them
4 · Name your accounts as you add them
The name field is optional and it is the one you will regret leaving empty: it is what appears under “From” on every offer, on every preparation, and in the confirmation of every deletion.The move: a name like
Main or Backup beats an address you have to read twice.5 · Finish or cancel a waiting payment before you go hunting
5 · Finish or cancel a waiting payment before you go hunting
While one waits, that account can neither buy anything else nor open its pick-up point map — the basket is shared. The banner shows it with its amount, on the dashboard and on the Vestiaire screen.The move: “Resume” if you intend to go through with it, “Cancel payment” otherwise. Cancelling also empties the basket, and it says whether that worked.
6 · Do not reconnect during an outage
6 · Do not reconnect during an outage
“Check not possible” means the marketplace did not answer. It is not a refusal, and reconnecting on it re-signs a healthy account for nothing — a burst of sign-ins is the best way to get an account locked.The move: wait, then check again. Only “Connection refused” or “Connection expired” call for a reconnection.
7 · After refused credentials, fix first and reactivate second
7 · After refused credentials, fix first and reactivate second
An account whose password is rejected is set aside immediately and never retried. The notification says what to do: “The account is disabled: fix it to switch it back on.”The move: change the password on Vestiaire, save it here, then switch the account back on. In that order — reactivating first only queues another refusal.
8 · Delete what you no longer use
8 · Delete what you no longer use
Idle accounts hold their dedicated address, and there are twenty of that grade in the whole pool.The move: before adding an account, delete one you have stopped using. That is the gesture that frees the slot — setting an account aside does not.
What surprises people
A freshly connected account shows “Not checked”, not “Connected”
A freshly connected account shows “Not checked”, not “Connected”
Nothing has probed a buying page yet, and the code’s validity does not answer that question. Showing green there would be a guess dressed up as a fact.
“Connected — to be renewed soon” is not a task
“Connected — to be renewed soon” is not a task
It is information. Three days before the end, we start saying it; the account keeps buying until its last day.
An account with no end date is treated as expiring
An account with no end date is treated as expiring
Not knowing is not the same as being fine. When the date cannot be read, we warn rather than reassure.
Adding an account can be refused because a slot is taken elsewhere
Adding an account can be refused because a slot is taken elsewhere
Dedicated addresses are a shared, finite stock. The refusal names the reason instead of pretending the credentials were wrong.
The card point can read “Not applicable”
The card point can read “Not applicable”
On an account whose payment family is PayPal, asking for a card would invent a gap. That value is a normal outcome, not an error.
Deleting an account also erases its saved card
Deleting an account also erases its saved card
Whatever the vault held for it — the security code, and the number too when rega kept the whole card — goes before the line itself. Otherwise those secrets would outlive the account with nothing left able to reach them.
Your password never comes back to your screen — not even shortened
Your password never comes back to your screen — not even shortened
Neither does the sign-in code: its first characters are the account’s identifier. Your screen only learns that a code exists and that a password exists.
rega refuses details Vestiaire hands over willingly
rega refuses details Vestiaire hands over willingly
Postal address, postcode, date of birth, the holder’s own e-mail address: all served by the marketplace, none carried by us. A buying tool has no use for them.
A voucher of “10 %” is written exactly like that
A voucher of “10 %” is written exactly like that
Vouchers are quoted as the marketplace writes them, percentages and amounts alike. We do not reformat a value we did not compute.
Correcting your identity is announced as sent, never as saved
Correcting your identity is announced as sent, never as saved
Vestiaire answers that request without saying what it kept. So we say it went out, and stop there.
What this does not do yet
We would rather write it here than let you find out halfway through.No list of your Vestiaire favourites
Setting a heart works; listing them does not. The marketplace returns bare identifiers with no title, no photo and no price, and resolving them costs one read per item — thirty at a time, on demand. The panel that showed them was taken off the account page: this feature is moving elsewhere in rega.
A heart is removed on Vestiaire, not here
No gesture in rega takes one back. We would rather not offer a button that could fail silently on the wrong item.
There is no “Your offers” screen
Offers go out, and one message still refers to “your offers” — that screen does not exist today. An offer we could not record still went out; never replay it.
Vestiaire purchases are not in Orders
The Orders screen knows nothing of this marketplace yet: no purchase history, and no state read back after a payment has been requested.
Following an item does not favourite it
Adding a Vestiaire item to your watchlist sets no heart on the marketplace. The two gestures are separate, on purpose: the identifiers of the two marketplaces overlap, and a heart sent to the wrong one would land on a real, unrelated listing.
Nothing warns you when an account simply reaches its end
With no password on record, the connection runs out and buying stops. There is no failure to report at that moment, so there is no message — which is exactly why the status line says “no password on record” from the day you add it.
Where to go next
The marketplace
Why the work is not the same here as on Vinted, and what one shared watch means.
Making an offer
The floor, where it comes from, and why it rises to your amount and never comes back down.
Buying on Vestiaire
The two steps, the shared basket, and what an item really costs once the marketplace has added its lines.
Writing a filter
Every criterion, what it costs, and what happens when two of them contradict each other.
The Vestiaire screen
The Accounts tab in place, next to the radar and the detections.
The Accounts screen
The full account page: health strip, address book, card, delivery, pick-up points.