Skip to main content

​
Scopes

  • Account Information 🔒
  • Payment Initiation 🔒

​
Sandbox Environment

  1. Upload your eiDAS certificates (QWAC and QSEAL) into Yapily’s certificate vault.
  2. Add Postbank Sandbox from the Sandbox tab to your Yapily Console 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 for login information Create Consent Requests: user credentials must be present in the body request. e.g: Account / Payment init Consent 
"userCredentials" : {
	"id" : "6154057725"
	"password" : "PISPWD12"
}
If you see this error in the response: 
{
    "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 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 section for more details.
  1. Upload your eiDAS certificates (QWAC and QSEAL) into Yapily’s certificate vault.
  2. Add Postbank Live from the Live tab to your Yapily Console 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] [0-9] 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.

​
Support

If you require technical support with certificate management, please contact Support.