> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yapily.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Postbank

## Links

* [Deutsche Bank Developer Portal](https://developer.db.com)

* [Deutsche Bank TPP Registration](https://developer.db.com/registration)

## Scopes

* Account Information 🔒
* Payment Initiation 🔒

## Sandbox Environment

1. Upload your eiDAS certificates (QWAC and QSEAL) into Yapily's [certificate vault](https://console.yapily.com/certificates).
2. Add **Postbank Sandbox** from the **Sandbox** tab to your [Yapily Console](https://console.yapily.com/applications) application.
3. Add this institution into your app from the `Sandbox` tab and configure the institution by selecting the `certificates` from the dropdown.
4. Select your `QSEAL` and `QWAC` certificates from the relevant drop-downs lists then click *Save* to save the certificates.

See [Sandbox Credentials](/resources/sandbox/sandbox-credentials) for login information

**Create Consent Requests:** user credentials must be present in the body request. e.g:

**Account / Payment init Consent**

```json theme={null}
"userCredentials" : {
	"id" : "6154057725"
	"password" : "PISPWD12"
}
```

If you see this error in the response:

```json theme={null}
{
    "tppMessages": [
        {
            "code": "Unauthorized",
            "text": "This TPP is not registered.",
            "category": "ERROR"
        }
    ],
    "transactionStatus": "RJCT"
}
```

You have to do the registration onboarding process here: [Deutsche Sandbox Onboarding](https://developer.db.com/products/psd2#techdocs)

**Note:** Only Domestic Payments are available.

## Postbank Live Environment

**Precondition**: To connect to Deutsche Postbank. Also, you need a valid eiDAS certificates to connect to Postbank `Live` environment. Please refer [Deutsche Bank technical information](https://developer.db.com/products/psd2#techdocs) section for more details.

1. Upload your eiDAS certificates (QWAC and QSEAL) into Yapily's [certificate vault](https://console.yapily.com/certificates).

2. Add **Postbank Live** from the **Live** tab to your [Yapily Console](https://console.yapily.com/applications) application.

3. Add this institution into your app from the `Live` tab and configure the institution by selecting the `certificates` from the dropdown.

4. Select your `QSEAL` and `QWAC` certificates from the relevant drop-downs lists then click *Save* to save the certificates.

The productive API's can be accessed by any valid eIDAS certificate and there is no other prerequisites unlike sandbox (registration).

**Create Consent Requests:** As the same as Sandbox, for accounts and payments in the headers must be present:

* **psu-id** = `VALID_PSU_ID`

**Re-authorise Consent (PATCH):** Same as above, **psu-id** must be included.

For Live version, the **psu-id** format is FKDN (without subaccount number): 3 digit branch number + 7 digit customer number

Pattern: **\[0-9]{3} \[0-9]{7}**

**Notes:**

* **Only Domestic Payments are available.**
* Postbank does not update the payment status once the funds are received by the creditor and so the status of the payment will not update from `PENDING`.
* Postbank are migrating customer accounts to Deutsche Bank systems - the Embedded Authorisation approach will no longer be supported by Postbank and the default authentication will be handled by a [redirect to the bank followed by a callback to your registered redirectUrl](/open-banking-flow/user-authorisation/single-redirect).

## Support

If you require technical support with certificate management, please contact [Support](/resources/support).
