Your customers generated the contract. Stamping shouldn't send them to MyTax.
When your HRIS is where the contract gets signed, leaving your product for stamping is a compliance gap every customer feels. Route the signed PDF to Kenal via our Partner API — your customers stay in your flow; we run the STSDS submission and handle LHDN queries.
What changes for your customers
What changes for your customers
Stamping fires off from the contract they just signed in your HRIS. No separate login, no separate system.
Certificate comes back through the webhook and binds to the same record your HRIS already owns.
Our team handles appeals and post-submission queries offline on their behalf.
What changes for your business
"Yes, we handle Malaysian stamp duty" becomes a pitch answer, not a compliance gap.
Customers that were evaluating competitors for compliance now stay.
Referral code at signup. Commission terms set in partnership agreement.
The things that go away
The "and for stamping you use MyTax" sentence in your onboarding docs.
Customer complaints about Malaysian compliance gaps.
The sales cycle stall when the prospect asks about stamp duty and your answer is "you'd have to figure that out."
Under the hood
For your engineering team.
POST /api/integration/employment/submit
ContractConfirmed, ContractProcessing, ContractCompleted, ContractFailed
HMAC-SHA256 with per-partner credentials.
See the Integration Quickstart and API Reference.
Integration, answered.
Yes. Each customer has their own wallet and certificates. Clean billing and compliance separation.
ContractConfirmed, ContractProcessing, ContractCompleted, ContractFailed.
Handled offline by our team. No MyTax login for your customer.
Admin-provisioned referral code. Commission percentage and duration per your partnership agreement.