Change User Default Gateway

POST /merchant/user/change_gateway

Change User Default Gateway

cURL

curl --request POST \
  --url https://api.unibee.dev/merchant/user/change_gateway \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "gatewayId": 123,
  "userId": 123,
  "gatewayPaymentType": "<string>",
  "gatewayUserId": "<string>",
  "paymentMethodId": "<string>"
}
'

200

{
  "code": 123,
  "data": {},
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

POST https://api.unibee.dev/merchant/user/change_gateway

Change User Default Gateway

---

Authorization

All UniBee Merchant API requests require authentication via API key.

Header	Required	Description
Authorization	Yes	Bearer <your_api_key>
Content-Type	Yes	application/json (for request body)

---

Parameters

Parameters for this endpoint are listed below. The schema is also shown in the Try it panel.

Request body

Name	Type	Required	Description
gatewayId	integer	Yes	GatewayId
gatewayPaymentType	string	No	GatewayPaymentType
gatewayUserId	string	No	GatewayUserId, verify and save GatewayUserId via gateway
paymentMethodId	string	No	PaymentMethodId of gateway, available for card type gateway, payment automatic will enable if set
userId	integer	Yes	User Id

---

Request examples

cURL

curl -X POST "https://api.unibee.dev/merchant/user/change_gateway" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "gatewayId": 0,
  "gatewayPaymentType": "",
  "gatewayUserId": "id_example",
  "paymentMethodId": "id_example",
  "userId": 0
}'

Sandbox

curl -X POST "https://api-sandbox.unibee.top/merchant/user/change_gateway" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "gatewayId": 0,
  "gatewayPaymentType": "",
  "gatewayUserId": "id_example",
  "paymentMethodId": "id_example",
  "userId": 0
}'

---

Response

Success responses return a JSON envelope with code, data, message, redirect, and requestId. code 0 indicates success. The response schema for this endpoint is shown below.

---

Error handling

HTTP status	Meaning
400	Bad request — invalid or missing parameters. Check message in the body.
401	Unauthorized — missing or invalid API key.
404	Not found — invalid path or resource.
500	Server error — retry with backoff.

When code in the response body is non-zero, check message for details. Use requestId when contacting support.

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

gatewayId · integer<int64> · required

GatewayId

userId · integer<int64> · required

User Id

gatewayPaymentType · string<string>

GatewayPaymentType

gatewayUserId · string<string>

GatewayUserId, verify and save GatewayUserId via gateway

paymentMethodId · string<string>

PaymentMethodId of gateway, available for card type gateway, payment automatic will enable if set

Response

200 - application/json

code · integer<int>

data · object

merchantId · integer<int64>

message · string<string>

redirect · string<string>

requestId · string<string>