Prerequisite: Saved customer and token
Create and manage thecustomer_id and token_id in Saved Payment Methods. A confirmed customer_id and token_id are required before you create a subscription.
1. Create Product
POST/product/v1/create
Creates a recurring billing product.
Request Parameters
In the sandbox environment,
minutes and hours can be used in the interval field for testing purposes.Response
Returns generatedproduct_id.
6. Update Product
POST/product/v1/update
Updates product metadata.
Request Parameters
Response
Returns number of affected rows.7. Query Products
POST/product/v1/query
Search for products.
Request Parameters
Response
List of matching products.8. Delete Product
POST/product/v1/delete
Deletes a product (must not be linked to active subscriptions).
Request Parameters
Response
Returns deleted product ID and row count.9. Create Subscription
POST/subscription/v1/create
Creates a recurring subscription.
Request Parameters
Products Object
Example Request
Response (data field)
10. Update Subscription
POST/subscription/v1/update
Request Parameters
Response (data field)
11. Query Subscription
POST/subscription/v1/query
Request Parameters
Sample Response
12. Cancel Subscription
POST/subscription/v1/cancel
Request Parameters
13. Query Subscription Orders
POST/subscription/billing_order/v1/list
Request Parameters
Response (data field)
14. Manual Charge Subscription
POST/subscription/v1/charge
Request Parameters
This API is only valid for subscriptions with failed billing and state
UNPAID, INCOMPLETE, or PAST_DUE.- If manual charge occurs before next billing time → subscription remains
ACTIVE - If manual charge occurs after next billing time → subscription will be cancelled
- If manual charge fails → subscription state remains unchanged
Query a saved payment token
POST/token/v1/query
Query token details, including the token expiry date. Use customer_id and token_id when you need a specific saved payment method. For the saved-payment-method flow and notification handling, see Customer & Token Setup.

