elepayFAQ for Server
Webhook
| Item | Question | Answer |
|---|---|---|
| Retry logic | If a webhook cannot be delivered, will it be retried? | Initially, retry 3 times at 1-minute intervals; then retry 3 times at 10-minute intervals |
| Configuration unit | Can we configure different URLs per store? | Configuration is at the application level. Use the locationId in the webhook notification to determine the store. |
| Notification type | Are webhooks sent on payment failure? | There are no webhook notifications for payment failures. When using charge, poll for the payment status in your backend and, if it becomes failed, design your flow to allow a new attempt. When using EasyQR, if a failure occurs while the code is still valid, the user can select a payment method and try again; therefore waiting until the code expires is recommended |
| Propagation time | Is it applied immediately after saving in the dashboard? | Yes, applied immediately. Because multiple configurations are possible, we recommend deleting the old URL after the switch is complete |
frontUrl
| Key Word | Question | Answer |
|---|---|---|
| Browser tab | After payment completes and it navigates to frontUrl, does it open in the original tab or a new tab? | Credit card: navigates in the original tab. When an app launches for code payments, the navigation to frontUrl opens in a new tab |
| Private mode | If the browser opens in private mode, can it navigate to frontUrl correctly? | Yes, navigation works in private mode. |
| Where navigation occurs | Does the navigation to frontUrl happen on the merchant’s QR display screen or on the user’s smartphone after payment? | Navigation occurs on the device that accesses the code URL, so it navigates on the user’s smartphone |
| Navigation condition | Is navigation possible only when using checkout? | Navigation is triggered by accessing codeUrl, so it is also possible when using only the Code API |
charge
| Key Word | Question | Answer |
|---|---|---|
| Authorization/Capture | Can authorization and capture be performed at different times? | For credit cards and Apple Pay/Google Pay, yes. 【How to implement】 Set capture=false in create charge to obtain an authorization. Finalize the sale via capture charge. 【Notes】 Credit cards and Google Pay support only equal-amount or reduced-amount captures. Apple Pay supports only equal-amount captures |
EasyQR
| Key Word | Question | Answer |
|---|---|---|
| orderNo | Can orderNo be duplicated? | orderNo must be unique within the same application. |
| What error code will be returned if a duplicate orderNo is sent? | Current behavior: for a completed transaction, or when re-generating within the validity period of an already generated code with the same orderNo, the following error is returned: "code": "9_000_000_40022","errorCode": "M002007","message": "該当注文番号はすでに支払済み。"Therefore, you can re-create with an orderNo used for a transaction canceled via Close EasyQR or canceled due to expiration. |
API keys
| Key Word | Question | Answer |
|---|---|---|
| Reissue | When an API key is reissued, is there an overlap period between the old and new keys? | They coexist for up to 3 days, but we recommend switching as soon as possible |
| Management unit | Do we need to manage API keys separately for each store? | API keys are managed per application (brand). |
| Secret/Public key | Do Create EasyQR code / Retrieve EasyQR code / Close EasyQR code all use the “secret key”? | All of Create EasyQR code / Retrieve EasyQR code / Close EasyQR code use the secret key. It is used via either Basic or Bearer authentication. |
| Secret/Public key | In the JavaScript SDK, is the key used in new Elepay(key, options) the “public key”? | The key specified for new Elepay(key, options) in the JavaScript SDK is the public key. It is used on the frontend for generating payment tokens, etc.; use the value labeled “Public Key” in the dashboard. |
Last updated on