Your users sign. Kenal stamps. The flow never breaks.
In Malaysia, a signed instrument isn't enforceable until it's stamped. When your customer's signature completes, hand the PDF to Kenal via the Partner API — stamping runs through STSDS, certificate comes back to your record. Your users don't bounce to MyTax.
What changes for your customers
What changes for your customers
Sign, then stamp — done. Without a context switch to MyTax or a separate login.
The same record your platform already owns. No separate filing system for stamped documents.
Our team handles appeals and post-submission queries. Your customer doesn't have to triage stamping support.
What changes for your business
Users who sign and stamp in your product don't evaluate alternatives for the stamping half.
Competitors routing users to MyTax look incomplete next to a platform that handles both.
Commission on every customer you introduce, per the partnership agreement.
The things that go away
"After you sign, go to MyTax to stamp" in your help docs.
User drop-off between signature and enforceability.
The competitive vulnerability where a user evaluates a signing platform that bundles stamping.
Under the hood
For your engineering team.
POST /api/integration/employment/submit
POST /api/integration/loan/submit
ContractConfirmed, ContractProcessing, ContractCompleted, ContractFailed
HMAC-SHA256 with per-partner credentials.
Employment and loan via API today. Tenancy and general contracts stamp through the Kenal web app.
Integration, answered.
Employment and loan today. Tenancy and general contracts go through the web app.
As the body of the submission payload. We store it alongside the certificate.
ContractFailed webhook fires. Our team reaches out to the customer directly to resolve.
Yes. Each customer has their own workspace, wallet, and certificates.
Referral code at signup. Commission percentage and duration per your partnership agreement.