These errors can occur due to several factors. Below are some common examples.
| Type | Function / API | Cause (Example) |
| Payment | pp.render | ・One of amount, merchantPaymentId, or requestedAt is not set ・merchantTimeoutAt is set to 0 or a past value |
| pp.createOrder | ||
| Login | pp.render | ・The domain of redirectUrl is not registered on the PayPay side Please contact your PayPay sales representative or the Smart Payment implementation support desk with the domain information |
| pp.getLoginUrl | ||
| /v2/smartpayment/qr/sessions |
When BAD_REQUEST is returned by pp.getLoginUrl
If pp.getLoginUrl returns BAD_REQUEST, please verify that the request content matches the settings in PayPay for Developers.
- Confirm that the domain of
redirectUrlmatches the registered Callback URL or callback domain. - Verify that the
clientIdcorresponds to the target environment and service. - Check that required request values such as
redirectType,codeChallenge, andnonceare not missing.
If the issue persists, please contact us with the environment where the error occurred, request date and time, error details, configured Callback URL, and the main parameters of the relevant request.