1688 Procurement
1688 Payment URL MCP
Get a payment link for a 1688 order so you can complete payment yourself. Requires an active 1688 authorization and your Nexscope API key.
1688 Payment URL AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Get A Link For Manual Payment
Prompt: For my 1688 orders [ORDER_IDS], explain that I must complete payment myself. After I explicitly confirm requesting the link, send confirmGetPaymentUrl=true and show the returned payUrl and success status. Do not open the URL or pay automatically.
What You Need to Provide
Replace bracketed values with your own identifiers and inputs. Use only your own ACTIVE, unexpired 1688 store authorization.
Read the returned business status and message. An HTTP or envelope success does not prove that an order or write operation succeeded.
Obtain separate, explicit user confirmation before setting the documented confirm flag to JSON true. Never retry a write automatically.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_data_alibaba1688_payment_urlhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "1688-payment-url-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_payment_url",
"arguments": {
"confirmGetPaymentUrl": false,
"orderIdList": [
"3309156590237728779"
]
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
confirmGetPaymentUrl | boolean | required | Must be JSON true after separate explicit user confirmation. Examples default to false and do not authorize this action. Default: false |
orderIdList | array | required | orderIdList Minimum items: 1 |
orderIdList[] | string | required | Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$ |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | optional | Nexscope transport/business envelope code; 0 means the request was processed. Inspect data for operation outcomes. |
cost | string | optional | Processing time in milliseconds, not credits. |
data | object | optional | Data value used by this API operation. |
data.errorCode | string | optional | Error code value used by this API operation. |
data.errorMessage | string | optional | Error message value used by this API operation. |
data.payUrl | string | optional | Display for manual payment; do not open or pay automatically. |
data.success | boolean | optional | Success value used by this API operation. |
msg | string | null | optional | Safe response message. |
time | string | optional | Server response time. |
traceId | string | null | optional | Request trace identifier. |
ts | string | optional | Server timestamp. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
For my 1688 orders [ORDER_IDS], explain that I must complete payment myself. After I explicitly confirm requesting the link, send confirmGetPaymentUrl=true and show the returned payUrl and success status. Do not open the URL or pay automatically.
Suggested Steps
After separate explicit confirmation, request the payUrl for the selected orders. Display the link for manual payment; do not open it or pay automatically.
About this sample: This is a workflow guide, not a verified API response. The example does not execute the write or confirm its outcome.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Workflow example, not a verified API response.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
No verified MCP request example is available. Refer to Integration and the documented requirements before preparing a call.
MCP Response Format
This workflow does not claim an API result. No verified response example is available; refer to Parameters & Response for the documented response structure.