Build on PSE.

Modern APIs for new builds, and ISO 8583, host-to-host, SFTP files and signed form posts for systems that already work.

Quickstart

Create a paymentPOST /v1/payment_intents
curl https://api.tr.psecore.com/v1/payment_intents \
  -H "Authorization: Bearer sk_test_..." \
  -H "Idempotency-Key: 7c0e5a52-5d0f" \
  -d amount=125000 \
  -d currency=TRY \
  -d "installments[count]=6" \
  -d confirm=true
{
  "id": "pi_3QbR...",
  "status": "succeeded",
  "amount": 125000,
  "installments": { "count": 6 }
}

SDKs

  • Node
  • Python
  • PHP
  • Java
  • .NET
  • Go
  • Rust
  • iOS
  • Android

Tools

  • pse CLILog in, forward sandbox webhooks to your machine and trigger test events.
  • SandboxA sandbox in every market.
  • MCP serverAn MCP server for coding agents.

Sandbox opens with the pilot

$ pse login
$ pse listen --forward-to localhost:3000/webhooks
  Ready. Forwarding sandbox events.
$ pse trigger payment_intent.succeeded
  200 payment_intent.created
  200 payment_intent.succeeded

Integration styles

Hosted checkout

A payment page hosted by PSE, with installments, 3DS and local methods, in English, Turkish and Arabic.

Card fields

Card inputs served by PSE Vault inside your own checkout, so card data never reaches your servers.

Mobile SDKs

Native iOS and Android SDKs for payments inside your app.

Cloud Terminal

Start a payment on a PSE Terminal from any till with one REST call and get the result by webhook.

ISO 8583 terminals

Connect the terminals you already have to PSE Switch over TLS with AES or TDES DUKPT.

Host-to-host

ISO 8583 over IPsec or mTLS, or REST with client certificates, for ISOs, PSPs and large retailers.

Form post

Signed form posts compatible with common Turkish virtual POS integrations.

SFTP batch

PGP-signed charge files over SFTP, fixed-width or CSV, for batch and recurring payments.

Move your payments to one core.

Tell us your market, channels and volumes. We will plan the integration with you.

Get sandbox keysTalk to sales