Key Points
- If the payload is pre-filled with data (e.g., amount, currency, customer details, return_url, payment method), these details will be reflected on the HPP, providing a streamlined user experience.
- If the payload lacks certain data, the customer will need to manually enter the missing information on the HPP.
- Ensure that the necessary headers and authentication details are included to successfully generate the HPP link.
Flow diagram
ApplePay & GooglePay
When a merchant is configured for Apple Pay and Google Pay, the Hosted Payment Page (HPP) will display buttons for Google Pay and Apple Pay, allowing customers to complete payments through these methodsKey Points
Api Parameters
Authorizations
API Key for Authorization. Format: 'Basic YOUR_API_KEY_HERE'
API Key specific to x-api-key.
Body
The request payload to generate an HPP link.
A JSON object containing the Return URLs.
The processing currency (e.g., JPY).
3
"JPY"
The merchant ID (DASMID).
128
"< Merchant ID >"
The email address of the Merchant.
45
"merchant@testemail.com"
A JSON object containing the billing address of the cardholder.
The amount of the transaction.
1000
The merchant transaction reference ID.
45
"2003089893366DTEST"
A JSON object containing the shipping address of the cardholder.
Response
HPP link generated successfully
The transaction reference ID.
"f49173ce-4916-445c-a831-3c1468acf14e"
The URL Link of the hosted payment page link generated.
"https://checkout-dev.paymentoptions.com/jp/HostedPaymentPage/hKJsdByR"
The amount of the transaction.
1000
The processing currency of the transaction.
"JPY"
The merchant transaction reference ID.
"2003089893366DTEST"
The DAS merchant ID of the transaction performed.
"< Merchant ID >"
The email address of the Merchant.
"merchant@testemail.com"
A JSON object containing the Return URL.
A JSON object containing the billing address of the cardholder.
A JSON object containing the shipping address of the cardholder.