Overview
Depot is a redirect-based e-money payment method. After creating a payment via API, redirect the customer topayment_url to complete the payment.
Requirements
Field Constraints
Depot validates these fields more strictly than card payments, and it does so late: creating the payment succeeds, and the violation only surfaces when the customer tries to pay on the Depot page. Validate these yourself before calling the API — otherwise the customer is redirected, fills nothing in, and hits an error you cannot explain to them.customer_id, email, tel and product_name are shown to the customer on the payment page, so send them whenever you have the values.
Payment Flow
1
Create Payment
Call
POST /v1/payments to create a payment and obtain payment_url2
Redirect Customer
Redirect customer to
payment_url3
Customer Completes Payment
Customer completes payment on Depot’s page
4
Redirect Back
Customer is redirected to the
success_url / failure_url / cancel_url you passed on the payment, falling back to the defaults configured in your merchant dashboard5
Verify Result
Treat the webhook as the source of truth. Optionally confirm with the Get Payment API
Implementation Example
Webhook Integration
The webhook is the authoritative result of a Depot payment — confirm the payment there rather than relying on the page the customer lands on. Depot webhooks use the same payload as every other payment method:payment_method is "depot", currency is "jpy", and the card fields (card_brand, card_last4, …) are absent. Any metadata you sent when creating the payment is returned unchanged, which makes it a convenient place to carry your own session identifier.
For the complete payload and signature verification, see the Webhooks reference. For all request parameters, see API Reference.