bankcard-3-validate
Bank Card 3-Element Verification
Provides a bank card 3-element verification API service, enabling developers to quickly verify bank card information and integrate it into business systems.
Usage Cost
50 coins/call
Quick Start
Use a unified response envelope and call directly from your backend.
https://openapi.toolkk.com/v1/bankcard-3-validatecURL Example
curl --request POST \
--url 'https://openapi.toolkk.com/v1/bankcard-3-validate' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY' \
--data '{\n "name": "张三",\n "idcard": "110105199003078887",\n "bankcard": "6228480402564890018"\n}'Python Example
import os
import requests
url = "https://openapi.toolkk.com/v1/bankcard-3-validate"
payload = {
"name": "张三",
"idcard": "110105199003078887",
"bankcard": "6228480402564890018"
}
headers = {
"Content-Type": "application/json",
"X-API-Key": os.getenv("TOOLKK_API_KEY", "YOUR_API_KEY"),
}
response = requests.request("POST", url, headers=headers, json=payload, timeout=30)
response.raise_for_status()
print(response.json())Go Example
package main
import (
"bytes"
"fmt"
"io"
"net/http"
)
func main() {
endpoint := "https://openapi.toolkk.com/v1/bankcard-3-validate"
payload := []byte("{\n \"name\": \"张三\",\n \"idcard\": \"110105199003078887\",\n \"bankcard\": \"6228480402564890018\"\n}")
req, err := http.NewRequest("POST", endpoint, bytes.NewBuffer(payload))
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("X-API-Key", "YOUR_API_KEY")
resp, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
if err != nil {
panic(err)
}
fmt.Println(string(body))
}Java Example
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class ToolkkExample {
public static void main(String[] args) throws Exception {
String payload = "{\n \"name\": \"张三\",\n \"idcard\": \"110105199003078887\",\n \"bankcard\": \"6228480402564890018\"\n}";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://openapi.toolkk.com/v1/bankcard-3-validate"))
.method("POST", HttpRequest.BodyPublishers.ofString(payload))
.header("Content-Type", "application/json")
.header("X-API-Key", "YOUR_API_KEY")
.build();
HttpResponse<String> response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}PHP Example
<?php
$endpoint = 'https://openapi.toolkk.com/v1/bankcard-3-validate';
$payload = "{\n \"name\": \"张三\",\n \"idcard\": \"110105199003078887\",\n \"bankcard\": \"6228480402564890018\"\n}";
$ch = curl_init($endpoint);
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_HTTPHEADER => [
'Content-Type: application/json',
'X-API-Key: YOUR_API_KEY',
],
CURLOPT_POSTFIELDS => $payload,
]);
$response = curl_exec($ch);
if ($response === false) {
throw new RuntimeException(curl_error($ch));
}
curl_close($ch);
echo $response;Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"result": "一致",
"desc": "姓名/身份证/银行卡一致"
}
}Examples illustrate the response structure. Actual results depend on the API response.
- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 10000 ms
Send your API Key in the X-API-Key header from your backend.
Check both HTTP status and business fields before treating a call as successful.
Use retries and backoff together with rate limits in high-frequency scenarios.
Request Fields
Send requests from your server with the key in the X-API-Key header.
Request Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| name | string | Unspecified | Unspecified | 张三 |
| idcard | string | Unspecified | Unspecified | 110105199003078887 |
| bankcard | string | Unspecified | Unspecified | 6228480402564890018 |
Request Example
{
"name": "张三",
"idcard": "110105199003078887",
"bankcard": "6228480402564890018"
}- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 10000 ms
Response Fields
Examples illustrate the response structure. Actual results depend on the API response.
Response Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| code | string | Unspecified | Unspecified | SUCCESS |
| message | string | Unspecified | Unspecified | success |
| data | object | Unspecified | Unspecified | {...} |
| data.result | string | Unspecified | Unspecified | 一致 |
| data.desc | string | Unspecified | Unspecified | 姓名/身份证/银行卡一致 |
Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"result": "一致",
"desc": "姓名/身份证/银行卡一致"
}
}API overview
Capabilities, use cases, limitations, and frequently asked questions.
Bank Card 3-Element Verification API Overview
The Bank Card 3-Element Verification API helps developers quickly process bank card authentication within their systems. It returns structured results and is ideal for scenarios such as real-name authentication, onboarding approval, and risk control interception.
Applicable Scenarios
- Integrate bank card 3-element verification capabilities into internal systems, SaaS platforms, automated workflows, or admin dashboards.
- Suitable for business scenarios requiring stable API calls, standardized responses, and orchestratable interface capabilities.
- We recommend combining this with rate limiting, failure retries, and result caching strategies to improve overall integration stability.
Integration Recommendations
- Before integration, confirm the request parameter format, authentication method, and error code handling logic.
- For high-frequency verification scenarios, it is recommended to implement log tracking, timeout control, and idempotency handling.
- If the results are used for risk control or automated decision-making, we recommend making secondary judgments based on business rules rather than relying solely on the API response.