Switzerland · PostFinance AG · EBICS
Connect PostFinance without learning EBICS.
EBICS 2.5 and 3.0 on Host ID PFEBICS, bank key hashes on a published datasheet, free of charge, with payment approval through the distributed signature. We handle the payments, the statements and every protocol step underneath.
The host, checked live
<ebicsHEVResponse xmlns="http://www.ebics.org/H000"> <ReturnCode>000000</ReturnCode> <ReportText>[EBICS_OK] OK</ReportText> <VersionNumber ProtocolVersion="H003">02.40</VersionNumber> <VersionNumber ProtocolVersion="H004">02.50</VersionNumber> <VersionNumber ProtocolVersion="H005">03.02</VersionNumber> </ebicsHEVResponse>
Host ID
PFEBICS
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.20 s
Published by the bank
PostFinance's organisation, history and BIC pages; the UID register, GLEIF and FINMA.
Bank details
| Legal name | PostFinance AG (PostFinance Ltd) |
| Legal form | Aktiengesellschaft (AG) — private limited company under private law |
| Registered office | Mingerstrasse 20, 3030 Bern |
| UID | CHE-114.583.749 |
| LEI | 5299000LHOLXRRD8L428 |
| BIC | POFICHBEXXX |
| Clearing number | 09000 |
| Owner | Swiss Post Ltd — fully-owned subsidiary |
| Supervision | FINMA — licence under the Banking Act, supervisory category 2 |
| Systemic importance | Declared a systemically important bank by FINMA |
| Business customers | +41 58 448 14 24 |
Checked live
Measured against the live host.
Access data
| EBICS address | https://ebics.postfinance.ch/ebics/ebics.aspx |
| Host ID | PFEBICS |
| Protocol versions | H003 (02.40), H004 (02.50) and H005 (03.02) |
Published by the bank
PostFinance's EBICS parameter datasheet, the legal provisions for EBICS registration, its EBICS factsheet and its technical channels manual.
Keys, signatures and the agreement
| Agreement | Registration for/modification to EBICS at PostFinance Ltd, with a registration for each service used (e.g. electronic payment order via file transfer) |
| Also applicable | PostFinance's General Terms and Conditions and Subscriber Conditions — the EBICS registration prevails where they differ |
| Price | EBICS free of charge |
| Versions on the datasheet | 3.0 and 2.5 — version 3.0 recommended |
| ISO 2019 messages | EBICS 3.0 is the technical requirement for exchanging them over EBICS |
| Authentication | X002 |
| Encryption | E002 |
| Electronic signature | A005 and A006 |
| Key length | Not published |
| Your keys | Generated in your EBICS software and sent with INI and HIA |
| Initialisation letters | INI and HIA letters signed and returned to PostFinance in the original; access is activated once all documents have arrived |
| Bank keys | Downloaded with HPB and checked against the hash values on the datasheet |
| Bank key hashes | Published on the datasheet for X002 and E002 — public-key hashes for EBICS 2.5, certificate hashes for EBICS 3.0 |
| Key changes | HCA (EBICS keys) · HCS (signature and EBICS keys) |
| Blocking access | SPR |
| Distributed signature | Supported — individual (I), transport (T) and collective A/B signatures, released in the EBICS client or the PostFinance EBICS App |
| Corporate seal | Individual or transport signature per user; orders are executed without further checks |
| Other release options | E-finance · Cash & Multibanking Tool (with a CMT contract) |
| Complaints | Immediately after access is set up, or within 30 days of delivery or execution for individual transactions |
| Files on the server | Until downloaded, for at most 12 months — no longer accessible after download |
| End of EBICS 2.5 | Not published |
Published by the bank
PostFinance's EBICS parameter datasheet (01765, PF 000019.00) and its technical channels manual.
Order types published by PostFinance
| 2.5 | What it does | 3.0 | BTF | Option | Container | Versions |
|---|---|---|---|---|---|---|
| XE2 | Payment order | BTU | MCT · CH · pain.001 | — | — | 03 · 09 |
| XL5 | PostFinance Direct Debit COR1 | BTU | DDD · BIL · pain.008 | CH001COR | — | 02 |
| XL6 | PostFinance Direct Debit B2B | BTU | DDD · BIL · pain.008 | CH001B2B | — | 02 |
| Z01 | Status report for pain.001 and pain.008 | BTD | PSR · CH · pain.002 | — | ZIP | 03 · 10 |
| Z52 | Intraday account statement | BTD | STM · CH · camt.052 | — | ZIP | 04 · 08 |
| Z53 | Account statement with or without detailed notification | BTD | EOP · CH · camt.053 | — | ZIP | 04 · 08 |
| ZS2 | Credit and debit notification | BTD | REP · CH · camt.054 | XDCI | ZIP | 04 · 08 |
| Z54 | Separate detailed notification | BTD | REP · CH · camt.054 | — | ZIP | 04 · 08 |
| STA | Account statement, SWIFT MT940 | BTD | EOP · CH · mt940 | — | Unzipped | — |
| VMK | Intraday account statement, SWIFT MT942 | BTD | STM · CH · mt942 | — | Unzipped | — |
| ZDF | PDF account documents | BTD | DAR · CH · documents | — | ZIP | — |
Versions read ISO 2009/2013 · ISO 2019. The camt.054 notification in Z54 carries the detailed notifications for the electronic payment order, CH-DD direct debit, returns, QR-IBAN, OSR and IBAN (SCOR/NON-SCOR).
These order types can be used only together with a Cash & Multibanking Tool contract:
System order types: key initialisation and changes, the bank’s keys and parameters, customer and subscriber data, the customer protocol, the distributed signature and blocking access. We run them during setup and afterwards.
Published by the bank
PostFinance's EPO manual, its acceptance cut-off page for electronically transmitted orders and its Subscriber Conditions for payment transactions.
Cut-off times and execution
| Same-day, EPO via file transfer (EBICS, MFTPF, SWIFT FileAct) | Collective orders delivered and released by 12 noon on banking days |
| Standard delivery, EPO | Until the banking day before the due date |
| Express orders, EPO | At most 100 transactions per order · latest transmission and approval 6 p.m. |
| Giro international, express | By 12.30 p.m. on the issue date |
| Giro international urgent, express | By 4 p.m. on the issue date |
| Cancellations and changes | Until the evening before the due date |
Acceptance cut-off times for electronically transmitted orders, in CET. V is the value date; V−1 means by 11.59 p.m. before it. Different times may apply before holidays.
| Region | Currency | Execution | Cut-off | Earliest credit |
|---|---|---|---|---|
| Switzerland and Liechtenstein | All available | Same day | 12 p.m. V | V to V+1 |
| Europe and rest of the world | All available | Same day | 12 p.m. V | V to V+2 |
| Switzerland and Liechtenstein | CHF, EUR | Standard | V−1 | V |
| Switzerland and Liechtenstein | AUD, CAD, GBP, JPY, NOK, DKK, SEK, USD | Standard | V−1 | V+1 |
| Switzerland and Liechtenstein | CHF, EUR, USD | Express | 1 p.m. foreign currency to a bank · 4 p.m. CHF to a bank · 6 p.m. to a postal account | V |
| Switzerland and Liechtenstein | AUD, CAD, GBP, JPY, NOK, DKK, SEK | Express | 1 p.m. foreign currency to a bank · 4 p.m. CHF to a bank · 6 p.m. to a postal account | V / V+1 |
| Worldwide | CHF | Express | 4 p.m. V | V |
| Worldwide | EUR | Express | 3 p.m. V | V |
| Worldwide | USD | Express | 4 p.m. V | V |
| Worldwide | CAD | Express | 12 p.m. V | V |
| Worldwide | CZK, GBP, HUF, NOK, PLN, SEK, ZAR | Express | 11 a.m. V | V |
| SEPA payments in SEPA countries · other euro payments | EUR | Standard | V−1 | V+1 |
| Other countries and currencies | Listed on PostFinance's acceptance cut-off page |
| Orders after the cut-off | Generally executed within two banking days |
| Late data | Processed in the next cycle if the due date has passed by at most 90 calendar days — older orders are not processed |
| Insufficient funds | Debit attempted every 30 minutes until 12 noon; with multiple debit attempts, retried over the next five banking days |
| End-of-period orders on a non-banking day | Generally executed on the preceding banking day |
| Collective orders | PostFinance may reject the entire order if individual payments are erroneous |
| Instant payments | Domestic only · not re-executed as a standard payment if they fail |
Published by the bank
PostFinance's Technical Specifications manual, EPO manual, electronic account documents manual and its address and ISO 20022 notices.
Formats
| pain.001 | Version 2009 (03) and version 2019 (pain.001.001.09, schema ch.03) — both accepted until November 2026 |
| pain.002 | Version 03 and pain.002.001.10 — returned in the version of the pain.001 submitted |
| Moving pain.001 to 2019 | No registration needed |
| camt.052 · camt.053 · camt.054 | Versions 04 and 08 |
| Moving camt to 2019 | Notify PostFinance in advance |
| camt.052 | Full or incremental — all entries since the last intraday statement |
| camt.053 | With or without detailed transactions · daily, weekly, fortnightly, monthly or quarterly |
| camt.054 | One per product — IBAN, QR-bill virtual account, OSR, CH-DD direct debit, returns |
| MT940 · MT942 | Delivered over EBICS — MT940 with or without entry code |
| PDF account documents | Account statement, interest statement and FX confirmations |
| Batch booking | True or false honoured · false allowed up to 100 transactions, above that set to true with a processing message |
| Salary payments (SALA) | Always shown as a batch booking |
| Charge bearer | DEBT or SHAR · SLEV only for SEPA payments |
| Service level | Only SEPA and SDVA |
| Debtor agent | BIC POFICHBEXXX or POFICHBE, or clearing number 9000 with code CHBCC |
| Creditor name | At most 70 characters |
| Character set | Swiss Payment Standards set — Basic Latin, Latin-1 Supplement, Latin Extended-A, plus Ș ș Ț ț and € |
| LEI · date-time in execution date | Not supported |
| Forwarding agent | Ignored |
| Unstructured addresses | Permitted until 13 Nov 2026 |
| Structured addresses | Mandatory from 14 Nov 2026 — town and country required |
| Hybrid addresses | Not supported — the payment is executed, the extra address lines are ignored |
| QR-bill | Structured addresses (type S) only since 22 Nov 2025 · unstructured ones processed until 13 Nov 2026 |
| End of MT940 | Not published |
BankConnector
What is built and shipped for this bank today.
What our engine produces
| Payment format | pain.001.001.09 (Swiss Payment Standards, ch.03 schema) |
| Guideline | PostFinance EBICS parameter datasheet (01765) |
| Charge bearer | SLEV on SEPA payments · SHAR on all others |
| Batch booking | False |
| Debtor BIC | Not required |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Character set | Latin — transliterated before the bank sees it |
| Payment types built | SEPA credit transfer · Swiss domestic transfer · QR-bill payment · international |
| Read back | camt, pain.002 — one normalised format |
| Not supported | Direct debits |
BankConnector
Questions
- What is PostFinance's EBICS Host ID and URL?
- Host ID PFEBICS, address https://ebics.postfinance.ch/ebics/ebics.aspx. PostFinance publishes both on its EBICS parameter datasheet, together with the hash values of its authentication (X002) and encryption (E002) keys.
- Which EBICS versions does PostFinance support?
- EBICS 3.0 and 2.5, with version 3.0 recommended; the host answers H003 (02.40), H004 (02.50) and H005 (03.02). EBICS 3.0 is the technical requirement for exchanging the 2019 ISO 20022 messages over EBICS. No end date for EBICS 2.5 has been published.
- Which keys and signature version does PostFinance require?
- X002 for authentication, E002 for encryption and A005 or A006 for the electronic signature. Your EBICS software generates your keys and sends them with INI and HIA; the signed INI and HIA letters go to PostFinance in the original. You download PostFinance's keys with HPB and check them against the datasheet: public-key hashes for EBICS 2.5, certificate hashes for EBICS 3.0.
- Does PostFinance support the distributed electronic signature?
- Yes. Payments can be released through the distributed signature with individual, transport and collective A/B signatures, in the EBICS client or the PostFinance EBICS App. The alternative is a corporate seal from your own software, in which case PostFinance executes the orders without further checks. Release in e-finance or the Cash & Multibanking Tool is also possible.
- Which order types does PostFinance use for EBICS 3.0?
- Payments upload as BTU MCT/CH/pain.001 and direct debits as BTU DDD/BIL/pain.008. Downloads are BTD: PSR/CH/pain.002, STM/CH/camt.052, EOP/CH/camt.053, REP/CH/camt.054 (with and without service option XDCI), EOP/CH/mt940, STM/CH/mt942 and DAR/CH for PDF account documents. The EBICS 2.5 equivalents are XE2, XL5, XL6, Z01, Z52, Z53, ZS2, Z54, STA, VMK and ZDF.
- What are PostFinance's payment cut-off times?
- PostFinance's EPO manual, which covers file transfer including EBICS, gives 12 noon on banking days for same-day collective orders, and 6 p.m. for express orders of up to 100 transactions. Its acceptance cut-off page for electronically transmitted orders gives 12 p.m. on the value date for same-day execution, and 11.59 p.m. the day before for standard execution (CET).
- What changes at PostFinance in November 2026?
- The transition period for the 2009 pain and 2013 camt versions ends in November 2026; systems must then handle the 2019 versions. Unstructured addresses in file-based payment orders are permitted until 13 November 2026, and structured addresses are mandatory from 14 November 2026. PostFinance does not support hybrid addresses.
- Can I connect my ERP to PostFinance?
- Yes. You send canonical JSON and BankConnector produces pain.001.001.09 to the Swiss Payment Standards ch.03 schema, then reads camt and pain.002 back into one normalised format. SEPA credit transfers, Swiss domestic transfers, QR-bill payments and international payments are supported. Direct debits are not.
Published by the bank
Dates the bank has announced. What we do about each one is ours.
Upcoming events in our register
The transition period for ISO 20022 version 2009 (pain) and 2013 (camt) ends. Processing systems must handle version 2019. Our engine already produces pain.001.001.09 for PostFinance.
Unstructured addresses are permitted until this date in electronic, file-based ISO 20022 payment orders, whose execution date must be before it. Processing of unstructured addresses on QR-bills is guaranteed until the same date.
Structured addresses become mandatory for all payment orders, with town and country required. PostFinance does not support hybrid addresses.
If all of this looks like a lot · it does not have to be
Five steps to a live PostFinance connection.
You do not need to know what any of the codes above mean. Our setup guide walks you through it one screen at a time.
- 1
Request the agreement from PostFinance
EBICS starts with paperwork. We draft the email, you send it, and you tell us when it has gone. There is nothing to configure until the bank replies.
- 2
Set up and send your keys
Enter the values from the agreement PostFinance returns. We already hold the ones that are public, so most of the form is filled in. Then one press generates your three key pairs and sends the public halves.
- 3
Prove your identity on paper
EBICS confirms the key exchange on paper, by design. We print the initialisation letter carrying the fingerprints PostFinance will check. You sign it by hand and send it.
- 4
Verify PostFinance and go live
While you wait, we fetch the bank's public keys and check them against the fingerprints it gives you over a separate channel. When that lands, you choose which approval policy governs payments here, and the connection switches on.
- 5
You are now in production with PostFinance
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — PostFinance’s technical business channels page, its EBICS parameter datasheet in English and German (01765), the legal provisions for EBICS registration/change (01769), its EBICS factsheet, its technical channels manual, its EPO manual, its Technical Specifications manual, its electronic account documents manual, its Subscriber Conditions for payment transactions, its acceptance cut-off times page, its address adjustments notice with its payment-order and QR-bill documents, its ISO 20022 version notice with its pain and camt documents, its BIC and SWIFT code page, its organisation page and its history page; the bank’s entries in the Swiss UID register, in GLEIF and in FINMA’s list of authorised banks. BankConnector is not affiliated with PostFinance AG.