Thinker Papyrus
Thinker Papyrus: eConsent and eContract on the Customer's Phone
Capture PDPA consent and sign legally binding loan contracts on the customer's phone, sealed with PKI and an electronic timestamp: Section 26 of the Electronic Transactions Act as standard, Section 28 on request.
- 0
- wet signatures or couriers
- s.26 / 28
- Electronic Transactions Act
- Minutes
- from approval to signed contract
Why paper slows lending
Approved loans still wait for a signature
The decision takes minutes; the paperwork afterwards can take days.
01
Couriers and branch visits
Contracts are printed, signed and shipped back, so disbursement waits on logistics.
02
Consent is hard to prove
Paper or checkbox consent is scattered across systems and difficult to show an auditor.
03
Errors found too late
A missing page or signature is found at document check, and the customer is called back.
What Papyrus does
Consent and contracts, signed and sealed digitally
Every document the customer agrees to, recorded once and provable later.
PDPA eConsent
Purpose-by-purpose consent, versioned, with withdrawal handled in the same place.
Contract templates
Contracts generated from approved templates with the loan's own terms filled in.
Sign on any phone
Customers read and sign with OTP on mobile, LINE OA or web, no app needed.
PKI signatures
Documents sealed with PKI to ETA Section 26 as standard, or Section 28 with a CA certificate.
Electronic timestamp
Each signature carries a trusted timestamp, so the moment of agreement is provable.
Audit-ready archive
Signed documents and the consent trail kept together and retrievable for audit.
How it works
From approval to a signed contract
Papyrus picks up where Expert Decision leaves off, and hands the contract to booking.
Collect consent
During onboarding the customer accepts PDPA and NCB consent, each recorded by purpose.
Generate the contract
Once approved, the contract is built from your template with the loan's terms.
Sign on the phone
The customer reviews and signs with OTP; PKI and a timestamp seal the document.
Book and archive
The signed contract goes to booking and is archived with its consent trail.
Buyer questions
How this is different
What teams weigh when comparing Papyrus with a general e-signature tool.
Why not a general e-signature tool?
Papyrus is built for lending: contracts are generated from the loan itself, consent is tied to the same customer record, and the signed file flows straight into booking.
Is the signature legally binding in Thailand?
Yes. Papyrus signs to Section 26 of the Electronic Transactions Act as standard, and Section 28 with a certificate from a licensed CA when you need it.
Can we use our own contract templates?
Yes. Your legal team's templates are loaded as they are, with fields mapped to the loan data.
Frequently asked questions
What teams ask about eConsent and eContract
The questions legal, compliance and operations teams ask before a demo.
See a contract signed in minutes.
Bring a contract template and we'll show it signed on a phone.