LinkPay Recipes (Legacy vs New)
This document provides detailed examples (Recipes) for both Legacy LinkPay API and New LinkPay (Interaction API), including request, response, and webhook samples.
Legacy API Example
Legacy LinkPay (POST)
Open Recipe
The Authorization header value must be a SHA256 signature generated by combining ordered parameters + secret key.
Legacy LinkPay (GET)
Open Recipe
Includes transactionInfo, pspTransInfo, paymentMethod, etc.
Legacy LinkPay (WEBHOOK)
Open Recipe
Uses Authorization from old signature.
New API Example
New LinkPay (POST)
Open Recipe
No need to build a sign string — the system authenticates directly using KeyID + Key.
The request structure remains 99% compatible with the legacy version.
New LinkPay (GET)
Open Recipe
Same structure but adds transInitiator.
New LinkPay (WEBHOOK)
Open Recipe
Now includes KeyID and SignType: Key-based in headers
Download the PDF Version:
Updated 4 days ago