Skip to main content
This page documents the available API endpoints for recurring payments. Make sure you have read the Recurring Overview before using these APIs.

1. Create Customer

POST /customer/v1/create Creates a new customer profile.

Request Parameters

Response

Returns the customer_id.

2. Update Customer

POST /customer/v1/update Updates an existing customer.

Request Parameters

Response

Returns number of affected rows.

3. Query Customers

POST /customer/v1/query Search for customers.

Request Parameters

Response

List of matching customers.

4. Delete Customer

POST /customer/v1/delete Deletes a customer. This action is irreversible.

Request Parameters

Response

Returns deleted customer ID and row count.

5. 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 generated product_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

You must create customer_id, product_id, and token_id before calling the subscription API.
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