Craftgate Payment API

Name: Craftgate Payment API API
Brand: Craftgate Payment API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey3 EndpointsREST

For Agents

Initialize, complete, and retrieve alternative payment method (APM) transactions on Craftgate for wallets like Kaspi, PayPal, and Klarna. Use when an agent needs to accept a regional or BNPL payment that is not a card charge.

Quickstart

Get started with Craftgate Payment API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"initialize an alternative payment method on craftgate"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Craftgate Payment API API.

Initialize an alternative payment method transaction and receive a redirect URL for the buyer

Complete an APM payment after the buyer returns from the wallet or BNPL provider

Retrieve the final status of an APM payment by paymentId

Switch between production and sandbox environments using the same endpoint structure

GET STARTED

Start building with Craftgate Payment API API

Explore with Jentic

View OpenAPI Document

Use for: Start a Kaspi payment for the customer's basket, Complete a PayPal APM payment after the redirect, Retrieve the status of payment ID 8841, Initialize a Klarna BNPL payment for 199 EUR

Not supported: Does not handle card processing, refunds, or merchant onboarding KYC — use for alternative payment method (APM) initialization, completion, and status retrieval only.

Craftgate is a payment orchestration platform widely used in Turkey and Central Asia, and the Craftgate Payment API exposes its alternative payment methods (APM) flow for accepting Kaspi, PayPal, Klarna, and other regional wallets and BNPL providers. The API provides three endpoints: initialize an APM payment to redirect the buyer, complete the payment after the buyer returns from the wallet, and retrieve the final payment status. Authentication uses an API key, and both production and sandbox servers are available.

Use Cases

Patterns agents use Craftgate Payment API API for, with concrete tasks.

★ Accept Kaspi Payments in Kazakhstan

An e-commerce checkout serving Kazakh shoppers calls POST /payment/v1/apm-payments/init with the order amount, currency, and apmType 'KASPI'. The response contains a redirect URL that sends the buyer to the Kaspi app to approve the charge. After the buyer returns, the merchant calls POST /payment/v1/apm-payments/complete and the order is marked paid. This adds a wallet that local shoppers prefer without a separate Kaspi integration.

Call POST /payment/v1/apm-payments/init with amount 25000, currencyCode 'KZT', and apmType 'KASPI', then redirect the buyer to redirectUrl from the response.

Klarna Buy Now, Pay Later Checkout

A merchant offers Klarna at checkout for European customers. POST /payment/v1/apm-payments/init with apmType 'KLARNA' creates the transaction and returns the Klarna hosted page URL. Once Klarna redirects the buyer back, /apm-payments/complete confirms the captured payment. The single Craftgate flow saves the merchant from running two separate APM integrations.

POST to /payment/v1/apm-payments/init with apmType 'KLARNA', amount 19900, currency 'EUR', then complete the payment with /apm-payments/complete using the returned token.

Reconciliation and Status Checks

A finance team reconciles APM transactions overnight. For each pending paymentId, the job calls GET /payment/v1/apm-payments/{paymentId} to retrieve the final status (approved, declined, or expired) and updates the order management system accordingly. This catches abandoned wallet payments that the buyer never completed.

For each unresolved paymentId in today's APM batch, call GET /payment/v1/apm-payments/{paymentId} and update the OMS with the returned status.

Agent-Driven Multi-Wallet Checkout

An AI checkout agent picks the right alternative payment method for each shopper based on their region and basket. It calls Craftgate's APM init endpoint with the chosen apmType, hands the buyer the redirect URL, and confirms with /complete on return. Through Jentic, the agent finds the right Craftgate operation by intent and uses the API key without seeing it in plain text.

Search Jentic for 'initialize alternative payment method on craftgate', execute POST /payment/v1/apm-payments/init with the shopper's chosen apmType, and hand back the redirect URL.

Key Endpoints

3 endpoints — craftgate is a payment orchestration platform widely used in turkey and central asia, and the craftgate payment api exposes its alternative payment methods (apm) flow for accepting kaspi, paypal, klarna, and other regional wallets and bnpl providers.

METHOD

PATH

DESCRIPTION

POST

/payment/v1/apm-payments/init

Initialize an alternative payment method transaction

POST

/payment/v1/apm-payments/complete

Complete an APM payment after the buyer redirect

GET

/payment/v1/apm-payments/{paymentId}

Retrieve the final status of an APM payment

POST

/payment/v1/apm-payments/init

Initialize an alternative payment method transaction

POST

/payment/v1/apm-payments/complete

Complete an APM payment after the buyer redirect

GET

/payment/v1/apm-payments/{paymentId}

Retrieve the final status of an APM payment

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Craftgate API keys are stored encrypted in the Jentic vault and injected as the request header at execution time. Agents never see the raw key.

Intent-based discovery

Agents search Jentic with intents like 'start a kaspi payment' or 'initialize an alternative payment' and Jentic returns the matching Craftgate APM operation with its input schema.

Time to first call

Direct Craftgate APM integration: 1-2 days for header signing, redirect handling, and complete-after-return logic. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

Stripe is a global payment processor that supports cards, wallets, and BNPL through Payment Intents.

Choose Stripe when the merchant operates globally and needs deep card and wallet coverage with one provider rather than a regional APM router.

Alternative

Adyen Checkout API

Adyen Checkout supports a wide range of local payment methods through a single integration.

Choose Adyen when a single-account global APM router is preferred and Adyen already covers the regional wallets needed.

Alternative

Mollie API

Mollie offers European-focused payment methods including iDEAL and Klarna.

Choose Mollie when the merchant is European-only and wants iDEAL alongside Klarna without onboarding multiple providers.

Complementary

PayPal Orders API

PayPal Orders is the underlying flow for PayPal as one of the APMs Craftgate routes.

Use PayPal directly when the merchant only needs PayPal and is willing to handle the redirect lifecycle without a Craftgate router.

FAQs

Specific to using Craftgate Payment API API through Jentic.

What authentication does the Craftgate Payment API use?

Craftgate uses an API key sent as a header on each request. Through Jentic, the API key is stored encrypted in the vault and added to outgoing requests at execution time, so it never appears in the agent's prompt or logs.

Can I accept Kaspi payments through the Craftgate API?

Yes. POST /payment/v1/apm-payments/init with apmType 'KASPI' returns a redirect URL that takes the buyer to the Kaspi app to approve the charge. After the redirect back, POST /payment/v1/apm-payments/complete finalises the transaction.

Does Craftgate support a sandbox environment?

Yes. The same three endpoints are available at https://sandbox-api.craftgate.io for end-to-end testing. Switch base URL only — request and response shapes are identical to production.

How do I check the status of an APM payment through Jentic?

Search Jentic for 'retrieve craftgate payment status', load GET /payment/v1/apm-payments/{paymentId}, and execute with the paymentId. The response contains the final status that should be reflected in the order management system.

What are the rate limits for the Craftgate API?

The OpenAPI spec does not declare numeric rate limits. Craftgate enforces fair-use limits in production. Production integrations should retry on 429 responses with exponential backoff and avoid synchronous polling loops.

Which alternative payment methods does this Craftgate spec cover?

This APM spec covers methods including Kaspi (Kazakhstan), PayPal, and Klarna, all flowing through the same three init/complete/retrieve endpoints by setting different apmType values. Card payments and refunds live on separate Craftgate APIs.