Yapı Kredi
Yapı ve Kredi Bankası A.Ş.
- BIC
- YAPITRISXXX
- BLZ (Germany)
- —
- Website
- www.yapikredi.com.tr
- Fee information
- Not verified
SEPA status — three separate layers
In SEPA, three concepts must not be conflated: a bank's registration in a scheme, offering it to customers and actually providing the service are different things. Below, these three layers are shown separately. "Not verified" = not independently confirmed; nothing is guessed.
1) Scheme status (four separate layers)
A green "Yes" is not given by legal obligation alone. For each scheme, four layers are shown separately: Legal scope · EPC register entry (authoritative) · Bank declaration · Customer access.
| Scheme | Legal scope | EPC register entry | Bank declaration | Customer access |
|---|---|---|---|---|
| SCT (SEPA Credit Transfer) | Not verified | No | Not verified | Not verified |
| SCT Instant | Not verified | No | Not verified | Not verified |
| SDD Core (direct debit) | Not verified | No | Not verified | Not verified |
| SDD B2B | Not verified | No | Not verified | Not verified |
| Verification of Payee (VoP) | Not verified | No | Not verified | Not verified |
EPC register source: European Payments Council — Register of Participants (2026-06-12). Because Turkey is outside SEPA, it does not appear in the EPC register.
SDD (direct debit) detail
SDD is not a single "Yes/No": the debtor side (collection from the account + refund) and the creditor side (collecting money) are different things.
SDD Core — EPC register entry
EPC Register of Participants (2026-06). Authoritative source.
SDD Core — debtor reachability (collection from account + refund)
At a bank registered in the scheme, a SEPA direct debit can be collected from the account; the refund right applies (8 weeks for authorised / 13 months for unauthorised).
SDD Core — creditor collection initiation (collecting money)
Collecting as a creditor requires a Creditor Identifier + collection infrastructure; whether this is offered to standard personal customers is not verified.
SDD B2B — EPC register entry
EPC Register of Participants (2026-06).
Creditor Identifier (CI) support
Whether the bank issues a CI to its customers has not been independently verified.
Refund / dispute function
Under SDD Core scheme rules the debtor has a refund right; the implementation detail varies by bank.
2) Customer availability and operational status
Because Turkey is not within the SEPA geographical scope, the SEPA schemes are not offered as a product to personal/business customers; euro transfers are made via SWIFT.
3) Message formats (ISO 20022)
| pain.001 (payment instruction) | Not verified |
| camt.053 (account statement) | Not verified |
| camt.054 (debit/credit notification) | Not verified |
4) Connection and API channels
"API" is not a single thing. PSD2 XS2A (regulated access for licensed third parties) is different from a public developer API or a corporate payment API.
PSD2 / Open Banking access interface (XS2A)
REGULATED access for licensed third parties (AISP/PISP) (Del. Reg. 2018/389). It is NOT a public developer API.
General / developer API product
Whether a public commercial developer API is offered has not been independently verified.
Corporate payment-initiation API (host-to-host)
Not verified.
EBICS
Corporate file-exchange protocol (mainly DE/FR/AT).
File upload / SFTP
Not verified.
Because Turkey is not yet within the SEPA geographical scope, this bank does not participate directly in the SEPA schemes; euro transfers are generally made via SWIFT.
Last verified: 16 July 2026
Sources
SEPA scheme rulebooks & geographical scope
European Payments Council (EPC)
- Document date:
- 2025
- Last checked:
- 2026-07-16
Spotted an error or want to suggest a current source? See our methodology.