Same code, as though you had walked up to the next desk on the journey.
No document this time. It was proven on the first run and it is still proven, so there is nothing left to check.
ShareRing Link
Four nodes. The same four at every desk.
A verified traveller, often before they have arrived.
Thailand, end to end
Two documents, two deadlines, one identity.
The eVisa and the TDAC are separate systems on separate clocks, and missing either one stops you at the border. ShareRing is built to serve both from a single verified identity, so the traveller proves who they are once rather than twice.
Thai eVisa: permission to enter
Official entry approval, required before you fly and determined by your passport nationality. Completed during trip planning.
TDAC: arrival processing
Mandatory for non-Thai travellers, visa or not. It replaces the paper TM6 arrival card and opens three days before the arrival date, to be submitted before landing.
Verified, reusable, secure
The identity behind the eVisa application is verified once and reused, rather than re-uploaded to each system in turn.
Prefilled, approved, fast-track
The TDAC can arrive prefilled from a credential the traveller already holds, so arrival processing becomes a scan rather than a form.
The document you carry is the proof, not the paperwork.
A traveller verifies identity once in ShareRing Me. The eVisa application and the arrival card can both draw on that same verified credential, so the passport is scanned once rather than uploaded twice to two agencies that cannot see each other.
What the traveller does
Once, at home: verify identity in the app and store the credential in a vault only they can open.
Before flying: apply for the eVisa with the identity already proved.
In the three days before arrival: submit the TDAC, which can be prefilled from the same credential.
At the border: present a QR code rather than a folder.
The eVisa and the arrival card are separate systems on separate clocks. The traveller proves themselves once and the same credential can answer both, which is the whole reason this is one workflow rather than two.
identity_documentPassport, NFC read at home rather than at a counter.
personal_infoThe fields both the eVisa and the TDAC ask for.
if_elsePassport valid and the details complete.
delivery_httpTo the eVisa system before departure.
delivery_httpTo the arrival card, in the three days before landing.
end_okA QR code at the border instead of a folder.
One capture, two deliveries. The passport is read once and never uploaded twice.
What is the difference between the Thai eVisa and the TDAC?
The eVisa is permission to enter, decided before you fly and determined by passport nationality. The TDAC is arrival processing, required of non-Thai travellers with or without a visa, and submitted in the three days before you land.
Does the traveller scan their passport twice?
No. It is read once, by NFC, at home. The same verified credential answers both the eVisa application and the arrival card.
Do the two systems talk to each other?
They do not, and that is the problem this solves. Both draw on the credential the traveller already holds, rather than each receiving its own upload.
What does the traveller show at the border?
A QR code rather than a folder of paperwork.
When does each step happen?
Verify at home while planning, apply for the eVisa before flying, and submit the TDAC in the three days before you land.
One journey. One identity.
Talk to us about carrying travellers from application to arrival on a single verified credential.
ShareRing Me
ShareRing Link
