A
Atlar API Guide
Step 6 — Make Your First Payment
6Step 6 of 10

Make Your First Payment

Create a SEPA Credit Transfer or cross-border payment.

Creating a SEPA Credit Transfer

With a source account ID (from Step 4) and a destination external account ID (from Step 5), you can create your first payment. If you completed those steps earlier in this guide, the IDs are pre-filled automatically.

POST
/payments/v2/credit-transfers

Create a single credit transfer payment. Requires source account ID and destination external account ID.

Find in Dashboard
Find in Dashboard
curl -X POST 'https://api.atlar.com/payments/v2/credit-transfers' \
  -H 'Authorization: Bearer ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "amount": {
      "currency": "EUR",
      "value": 2500
    },
    "date": "2026-03-26",
    "scheme": "SCT",
    "source": {
      "type": "ACCOUNT",
      "id": "{{sourceAccountId}}"
    },
    "destination": {
      "type": "EXTERNAL_ACCOUNT",
      "id": "{{externalAccountId}}"
    },
    "reference": "payout-12345"
  }'
Get a token on the Authentication step first
đŸ–Ĩī¸

Dashboard: Credit Transfers

View all credit transfers, their statuses, and approval states. Click into any payment to see the full audit trail.

app.atlar.com/credit-transfers

Payment schemes

The scheme field determines the payment rail used:

SchemeNameUse case
SCTSEPA Credit TransferEUR payments within SEPA zone
SCT_INSTSEPA InstantReal-time EUR payments
CROSS_BORDERCross-borderInternational / multi-currency payments
DOMESTICDomesticLocal payment schemes (Faster Payments, BGC, etc.)

Batch payments

For multiple payments at once, use the batch endpoint. You can include inline destinations (no pre-existing counterparty needed) with full routing details. The example below creates a cross-border USD payment:

POST
/payments/v2beta/credit-transfer-batches

Create a batch of credit transfers. Supports inline destinations with full routing details.

curl -X POST 'https://api.atlar.com/payments/v2beta/credit-transfer-batches' \
  -H 'Authorization: Bearer ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "treatment": "INDIVIDUAL_PAYMENTS",
    "payments": [
      {
        "amount": { "currency": "USD", "value": 3333 },
        "date": "2025-12-01",
        "scheme": "CROSS_BORDER",
        "source": {
          "type": "ACCOUNT",
          "id": "<source-account-id>"
        },
        "destination": {
          "type": "INLINE",
          "market": "US",
          "identifiers": [
            { "type": "Number", "number": "458003278449", "market": "US" }
          ],
          "routing": [
            { "type": "US_ABA", "number": "026009593" },
            { "type": "BIC", "number": "BOFAUS6S" }
          ],
          "holder": { "legalName": "Acme Inc." }
        },
        "reference": "invoice-789"
      }
    ],
    "skipValidationErrors": true
  }'
ℹī¸

Inline destinations

Inline destinations let you specify account identifiers, routing, and holder name directly in the payment request — without creating a counterparty first. This is useful for one-off or batch payments.

What happens next?

After creation, the payment has status CREATED. It must be approved before Atlar sends it to the bank. By default (security-first), the organization owner must approve every payment. See the next step to learn about approvals.

← PreviousCreate a CounterpartyNext →Approvals