Charge

​

How It Works

• A card token (obtained during card capture).
• The PSP name and credentials (or a stored credentialsId).
• The amount and currency.

​

Example: Charge with Inline Credentials

curl -X POST https://service.pcibooking.net/api/paymentGateway \
  -H "Authorization: APIKEY your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "PaymentGateway": {
      "Name": "YourPSPName",
      "Credentials": {
        "MerchantId": "your-merchant-id",
        "ApiKey": "your-psp-api-key"
      }
    },
    "CardToken": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4",
    "OperationType": "Charge",
    "Amount": 100.00,
    "Currency": "USD"
  }'

​

Example: Charge with Stored Credentials

curl -X POST "https://service.pcibooking.net/api/paymentGateway?credentialsId=my-stored-credentials" \
  -H "Authorization: APIKEY your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "CardToken": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4",
    "OperationType": "Charge",
    "Amount": 100.00,
    "Currency": "USD"
  }'

​

Key Points

• No card data in your request. Only the token. PCI Booking injects real card details during detokenization.
• PCI scope reduction. Your systems never touch sensitive card data.
• PSP-agnostic. The same endpoint works regardless of which PSP you route to. Change PSPs by updating your gateway credentials, not your code.
• Immediate settlement. Funds are charged and settled in a single step, unlike authorize-and-capture flows. Use a charge when you need immediate payment.
• 3DS is automatic. If the token has stored 3DS data and the PSP supports it, PCI Booking includes it automatically - see 3D Secure and the UPG.

​

Next Steps