---
title: "Initiate SEPA Payment"
method: POST
path: "/wallets/send/initiate/bank"
---

# Initiate SEPA Payment

`POST /wallets/send/initiate/bank`

## Request

- Base URL: `https://www.sandbox.striga.com/api/v1`
- URL: `https://www.sandbox.striga.com/api/v1/wallets/send/initiate/bank`
- Auth: API key in header `api-key` and API key in header `Authorization`

Send funds outwards from a EUR enriched account to another IBAN that is owned by the same person as the account holder.

## Headers

- `api-key` string, required
- `Authorization` string, required

## Request body

- object
  - `userId` string, required: The Id of the user who is sending this transaction
  - `sourceAccountId` string, required: The Id of the account to debit
  - `memo` string: An optional memo - Alphanumeric string upto 129 characters in length
  - `amount` string, required: The amount denominated in the smallest divisible unit of the sending currency. For example: cents or satoshis
  - `destination` object
    - `iban` string, required: IBAN of the recipient - must be in the name of the account holder, unless a third-party beneficiary `name` is declared below
    - `bic` string, required: BIC of the recipient - must be in the name of the account holder, unless a third-party beneficiary `name` is declared below
  - `fixedFee` string: Optional fixedFee in Euro cents to override the default application fee configuration. This amount can only be <= the default configured amount for this transaction type.
  - `percentFeeBps` string: Optional percentage fee in bps to override the default application fee configuration. This amount can only be <= the default configured amount for this transaction type.
  - `paymentType` string: Optional "paymentType" to force a payment scheme. Use it only if you absolutely need to, by default all payments go through SEPA_INSTANT if available and if not SEPA. In some rare cases if there is an issue with the scheme, this parameter can force trying with a particular method.
  - `whitelistedIbanId` string: ID of a whitelisted IBAN. if the IBAN is also a Trusted Beneficiary, the `totp` factor becomes available for this payment.
  - `verificationMethod` 'sms' | 'totp' | 'passkey': SCA factor for this payment — one of `sms` (default), `totp`, or `passkey`. `totp` requires the destination IBAN to be a Trusted Beneficiary.
  - `name` string: Optional. Declares a third-party beneficiary name for a one-off payout to the raw destination.iban/destination.bic below (not persisted as a beneficiary, and not usable together with whitelistedIbanId). The payout is always held for compliance review, and screened against sanctions lists when the application has enabled third-party payouts.

## Response `200`

200

- object
  - `challengeId` string
  - `dateExpires` string
  - `transaction` object
    - `syncedOwnerId` string
    - `sourceAccountId` string
    - `iban` string
    - `bic` string
    - `amount` string
    - `memo` string
    - `status` string
    - `txType` string
    - `parentWalletId` string
    - `currency` string
  - `feeEstimate` object
    - `totalFee` string
    - `networkFee` string
    - `ourFee` string
    - `theirFee` string
    - `feeCurrency` string
    - `fixedFeeDetails` object
      - `amount` string
      - `exchangeRate` string
      - `appliedFeeCents` string
    - `percentageFeeDetails` object
      - `amount` string
      - `appliedFeeBps` string

## Other responses

- `403`: 403

## Changes

- **2026-11-03** `0541ed1923c1`: 2 info
  - added the new optional request property `name`
  - added the non-success response with the status `403`

[Operation history](https://skmtc.dev/striga/apis/striga-v1/changes/wallets/send/initiate/bank/post.md)

---

[API](https://skmtc.dev/striga/apis/striga-v1.md) - [All operations](https://skmtc.dev/striga/apis/striga-v1/llms.txt) - [OpenAPI document](https://skmtc.dev/striga/apis/striga-v1/revisions/0541ed1923c1?raw)