API Reference

Integrate payment initiation directly into your backend architecture.

Authentication

All API requests must be authenticated using a Bearer token provided in the HTTP Authorization header.

                    Authorization: Bearer sk_live_...
                

Endpoints

`POST /v1/payments`

Initiate a new payment intent. Returns a redirect_url to forward the user to their bank.

`GET /v1/payments/{id}`

Retrieve the status of a specific payment. Used primarily for reconciliation if webhooks fail.

`POST /v1/refunds`

Initiate a programmatic payout back to the source IBAN of a previously settled payment.

Example Request

curl -X POST https://api.pisria.com/v1/payments \
  -H "Authorization: Bearer sk_test_123" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 15000,
    "currency": "EUR",
    "creditor_account": {
      "iban": "DE89370400440532013000"
    },
    "reference": "ORDER-9912",
    "redirect_uri": "https://merchant.com/success"
  }'

State Machine

Payments transition through the following states:

PENDING
AUTHORIZED
SETTLED
FAILED