RevKeenDocs
StatusSupport
API Reference
💳 Core PaymentsPayment Intents

Confirm a payment intent

Not available through the API yet. There is no way to supply a card token or a saved card here, so a confirm cannot charge: it returns 422 payment_method_unusable and leaves the payment intent unchanged. Take card payments with hosted checkout or a payment link. A server-side confirm for saved cards is planned.

POST/payment-intents/{id}/confirm

Not available through the API yet. There is no way to supply a card token or a saved card here, so a confirm cannot charge: it returns 422 payment_method_unusable and leaves the payment intent unchanged. Take card payments with hosted checkout or a payment link. A server-side confirm for saved cards is planned.

Related endpoints

  • POST /payment-intents — Create a payment intent
  • GET /payment-intents — List payment intents
  • GET /payment-intents/{id} — Retrieve a payment intent
  • POST /payment-intents/{id}/capture — Capture a payment intent
  • POST /payment-intents/{id}/cancel — Cancel a payment intent

Common errors

  • 400 invalid_request — malformed payload or failed validation.
  • 404 resource_missing — the referenced resource does not exist or is not visible to your key.
  • 422 unprocessable_entity — business-rule failure (for example, refunding more than the original charge).

Idempotency

Pass an Idempotency-Key header (UUID v4 recommended) to make retries safe. Keys are valid for 24 hours; see the idempotency guide.

Authorization

x-api-key<token>

Your RevKeen merchant API key. Create and manage keys in Dashboard → Settings → Developer. Use rk_sandbox_* for staging/test and rk_live_* for production. The same key may be sent as Authorization: Bearer <key> if that suits your HTTP client better. A missing, invalid, expired, or revoked key returns 401 with a WWW-Authenticate: Bearer challenge; a valid key without the required scope returns 403.

In: header

Path Parameters

id*string

Payment intent public ID (pi_…) or UUID.

Match^(?:pi_[A-Za-z0-9]+|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Parameters for confirming a payment intent. Optionally attach a payment method and specify a return URL for 3DS flows.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

Stuck on an error response? Ask the RevKeen assistant to explain it.
curl -X POST "https://api.revkeen.com/v2/payment-intents/pi_abc123/confirm" \
  -H "x-api-key: $REVKEEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "payment_method": "11111111-1111-4111-8111-111111111111",
    "return_url": "https://example.com/success"
  }'

Synthetic documentation data, validated against the response schema; not a live API result.

{  "id": "pi_k3m9x2q7w8e1r4t6",  "object": "payment_intent",  "amount": 5880,  "amount_capturable": 0,  "amount_received": 5880,  "currency": "gbp",  "customer": "c2a1e7d4-5b3f-4a8e-9d21-6f0b3e4c7a11",  "description": "INV-0042",  "last_payment_error": null,  "metadata": {},  "next_action": null,  "payment_method": "9e8d7c6b-5a4f-4e3d-8c2b-1a0f9e8d7c65",  "receipt_email": "ada.lovelace@example.com",  "statement_descriptor": "REVKEEN PRO",  "statement_descriptor_suffix": null,  "status": "succeeded",  "capture_method": "automatic",  "client_secret": "pi_k3m9x2q7w8e1r4t6_secret_example",  "canceled_at": null,  "cancellation_reason": null,  "created": 1776333720,  "transaction": "7b8c9d0e-1f2a-4b43-9d4e-5f6a7b8c9d42",  "livemode": true}