Charge existing user with saved payment method

post

https://api.web2wave.com/api/subscription/user/charge

Charges a user based on the selected web2wave price ID. Can initiate subscriptions and do one-time upsells.
Supported for existing users with a saved payment method on Stripe or Solidgate.

Solidgate 3-D Secure (3DS)

Solidgate 1-click upsells may require cardholder authentication. To support 3DS 2.0, pass the browser
fingerprint fields below (header_accept, header_accept_language, browser_*, time_zone_offset)
together with success_url / fail_url for post-authentication redirects.

The User-Agent header of the API request is forwarded automatically; you do not need to send it in the body.

If 3DS is required, the response returns success: true with a verify_url. Redirect the customer to
that URL to complete payment verification. After authentication, Solidgate redirects the customer to
success_url or fail_url, and the final order status is delivered via webhook.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

user_id

string

required

GUID of the user to be charged

price_id

integer

required

Internal Web2Wave price ID to be charged

subscription_id

integer

Internal Web2Wave subscription ID. This subscription ID will be used to find the specific subscription from which the payment data will be received. If not filled in, the data will be retrieved from the user's last active subscription.

wait_subscription

integer

Sometimes the payment provider delays sending webhooks, which may result in the subscription field being empty in the API response.
To increase the likelihood of receiving a response with the subscription field populated, set this field to 1.
When enabled, the system will wait up to 20–25 seconds for a response from Stripe or Solidgate before returning the result.

Important: Enabling this option may increase the total API response time to up to 30 seconds.
Not applicable when the response includes verify_url (3DS required) — redirect the user first, then poll subscription status after authentication.

header_accept

string

Solidgate only. Actual content of the browser Accept HTTP header.
Required for Solidgate 3DS 2.0. Example source: window.w2w_accept_page or the request Accept header.

header_accept_language

string

Solidgate only. Browser language from navigator.language (IETF BCP 47 recommended).
Required for Solidgate 3DS 2.0.

browser_color_depth

integer

Solidgate only. Screen color depth from screen.colorDepth.
Required for Solidgate 3DS 2.0.

browser_screen_height

integer

Solidgate only. Screen height in pixels from screen.height.
Required for Solidgate 3DS 2.0.

browser_screen_width

integer

Solidgate only. Screen width in pixels from screen.width.
Required for Solidgate 3DS 2.0.

browser_java_enabled

boolean

Solidgate only. Whether the Java plugin is enabled (navigator.javaEnabled()).
Required for Solidgate 3DS 2.0.

time_zone_offset

integer

Solidgate only. Timezone offset in minutes relative to UTC, as -new Date().getTimezoneOffset().
Required for Solidgate 3DS 2.0.

success_url

uri

Solidgate only. URL where the customer is redirected after successful 3DS authentication / payment.
Recommended when you expect a possible 3DS challenge.

fail_url

uri

Solidgate only. URL where the customer is redirected after failed 3DS authentication / payment.
Recommended when you expect a possible 3DS challenge.

Response

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Success or failure response