From bigcommerce-commerce
Integrates BigCommerce payments via Payment Processing API for headless setups: fetch methods, create access tokens, process payments, use stored instruments, with PCI guidance.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin bigcommerce-commerceThis skill is limited to using the following tools:
**Fetch live docs**:
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Fetch live docs:
https://developer.bigcommerce.com/docs/integrations/payments for payments guidesite:developer.bigcommerce.com payments processing api for Payment Processing APIbigcommerce payment methods api configuration for payment method managementBigCommerce handles payment gateway connections:
GET /v3/payments/methodsPOST /v3/payments/access_tokensPOST https://payments.bigcommerce.com/stores/{hash}/paymentsGET /v3/payments/methods?order_id={id} — returns accepted methods for an order:
{
"data": [
{
"id": "stripe.card",
"name": "Stripe",
"supported_instruments": [
{ "instrument_type": "VISA", "verification_value_required": true }
],
"test_mode": false,
"type": "CARD"
}
]
}
POST /v3/payments/access_tokens:
{
"order": { "id": 12345 }
}
Returns a single-use access token for the Payments endpoint.
POST https://payments.bigcommerce.com/stores/{hash}/payments
Headers:
Authorization: PAT {payment_access_token}Content-Type: application/json{
"payment": {
"instrument": {
"type": "card",
"number": "4111111111111111",
"expiry_month": 12,
"expiry_year": 2025,
"name": "John Doe",
"verification_value": "123"
},
"payment_method_id": "stripe.card"
}
}
Important: Sending raw card data requires PCI DSS compliance. Most implementations should use tokenized payment methods instead.
Customers can save payment methods for future purchases:
GET /v3/payments/methods?customer_id={id} — list stored instruments{
"payment": {
"instrument": {
"type": "stored_card",
"token": "abc123tokenvalue",
"verification_value": "123"
},
"payment_method_id": "stripe.card"
}
}
Payment methods configured in BigCommerce admin:
GET /v3/payments/methods — list configured payment methods:
Via V3 Payment Actions API:
POST /v3/orders/{id}/payment_actions/refund_quotes — get refund optionsPOST /v3/orders/{id}/payment_actions/refunds — process refundFor gateways supporting authorize-then-capture:
POST /v3/orders/{id}/payment_actions/void — void authorizationPOST /v3/orders/{id}/payment_actions/capture — capture authorized paymentIf you use the Payment Processing API with raw card data (type: "card"), your infrastructure must be PCI DSS compliant.
Fetch the BigCommerce Payment Processing API documentation for exact endpoints, request formats, and supported payment methods before implementing.