This page has been created and maintained by the relevant ASPSP, and OBIE takes no liability for the completeness nor accuracy of this data.

Note to ASPSP: Please indicate which brands this applies to and/or duplicate this page per brand if relevant.

ASPSP	Zempler Bank Limited
Brand	Zempler Bank
Date
Developer portal (s)	https://www.zemplerbank.com/api-developer/

Announcements

Improvement	Delivery date
v 3.1 Dynamic registration, identity/authentication and Account Information endpoints available for testing in Sandbox	26 Jun 2019
v 3.1.2 Account information endpoints available for testing in Production	28/Aug/19
v 3.1.2 Payment endpoints available for testing in Production	13/Sept/19
v 3.1.2 Funds Confirmation endpoints available for testing in Production	13/March/20
Change of name from Advanced Payment Solutions Limited (trading as Cashplus Bank) to Zempler Bank	09/July/24

On-boarding

Supports dynamic client registration (Y/N)	Y
Instructions for manual onboarding	n/a
OIDC .well-known endpoint	Sandbox: https://sandbox.identity.ob.zempler.tech/.well-known/openid-configuration Production: https://identity.ob.zempler.tech/.well-known/openid-configuration
Notes on testing
Other on-boarding notes	To on-board developers must: 1. Register/Enrol with Open Banking 2. Submit Software Statement Assertion to Client Registration endpoint Sandbox: https://sandbox.matls.identity.ob.zempler.tech/tpp/register Production: https://matls.identity.ob.zempler.tech/tpp/register When migrating from OB legacy certificates to the OBWAC and OBSEAL, new client must be created.
Documentation URL	https://www.zemplerbank.com/api-developer/ AISP: https://developer.zemplerbank.com/developer-guides/open-banking/account-information PISP: https://developer.zemplerbank.com/developer-guides/open-banking/payment-initiation

Sandbox PSU Accounts

Username	Password
JohnSmith	4eQY?$D%zm

Sandbox SCA authentication codes

Valid Code
12345678

Account Information API

Swagger version	Account and Transactions API (v3.1.2) https://developer.zemplerbank.com/docs/swagger_accounts.json
Base URI	https://sandbox.matls.api.ob.zempler.tech/open-banking/v3.1/aisp https://matls.api.ob.zempler.tech/open-banking/v3.1/aisp
General variances to specification	offline_access required in JWT request object scopes for refresh_token to be issued in authorisation flow
Non-functional limitations

Ref	Area	Field	Available (Y/N)	Exception/Notes (inc details on classification codes, field limits, and field formats)
1	Account Access Consents	POST /account-access-consents GET /account-access-consents/{ConsentId} DELETE /account-access-consents/{ConsentId}	Y	Permissions : ReadAccountsBasic ReadAccountsDetail ReadBalances ReadBeneficiariesBasic ReadBeneficiariesDetail ReadDirectDebits ReadScheduledPaymentsBasic ReadScheduledPaymentsDetail ReadStandingOrdersBasic ReadStandingOrdersDetail ReadStatementsBasic ReadStatementsDetail ReadTransactionsBasic ReadTransactionsCredits ReadTransactionsDebits ReadTransactionsDetail
2	Accounts	GET /accounts GET /accounts/{AccountId}	Y
3	Balances	GET /balances GET /accounts/{AccountId}/balances	Y
4	Beneficiaries	GET /beneficiaries GET /accounts/{AccountId}/beneficiaries	Y
5	Direct Debits	GET /direct-debits GET /accounts/{AccountId}/direct-debits	Y
6	Offers	GET /offers GET /accounts/{AccountId}/offers	N
7	Party	GET /party GET /accounts/{AccountId}/party	N
8	Products	GET /products GET accounts/{AccountId}/product	N
9	Scheduled Payments	GET /scheduled-payments GET /accounts/{AccountId}/scheduled-payments	Y
10	Standing Orders	GET /standing-orders GET /accounts/{AccountId}/standing-orders	Y
11	Statements	GET /accounts/{AccountId}/statements/{StatementId}/file	Y
12	Transactions	GET /transactions GET /accounts/{AccountId}/transactions GET /accounts/{AccountId}/statements/{StatementId}/transactions	Y	We only provide 24 months of transaction history

Payment Initiation API

Swagger version	Payments API (v3.1.2) https://developer.zemplerbank.com/docs/swagger_payments.json
Base URI	https://sandbox.matls.identity.ob.zempler.tech/open-banking/v3.1/pisp https://matls.api.ob.zempler.tech/open-banking/v3.1/pisp
General variances to specification
Non-functional limitations

	Area	Field	Available (Y/N)	Exception/Notes (inc details on classification codes, field limits, and field formats)
1	Domestic Payment Consent	POST /domestic-payment-consents GET /domestic-payment-consents/{ConsentId} DELETE /domestic-payment-consents/{ConsentId} GET/domestic-payment-consents/{ConsentId}/funds-confirmation	Y	Remittance information object is mandatory. At least one of the fields reference or unstructured must be provided.
2	Domestic Payment	POST/domestic-payments GET/domestic-payments/{DomesticPaymentId}	Y	Remittance information object is mandatory. At least one of the fields reference or unstructured must be provided.
3	Domestic Scheduled Payment Consent	POST /domestic-scheduled-payment-consent GET /domestic-scheduled-payment-consent/{ConsentId}	Y	Remittance information object is mandatory. At least one of the fields reference or unstructured must be provided.
4	Domestic Scheduled Payment	POST /domestic-scheduled-payment GET /domestic-scheduled-payment/{DomesticScheduledPaymentId}	Y	Remittance information object is mandatory. At least one of the fields reference or unstructured must be provided.
5	Domestic Standing Order Consent	POST /domestic-standing-order-consents GET /domestic-standing-order-consents/{ConsentId}	Y	Supported frequency: IntrvlWkDay:01 IntrvlWkDay:02 IntrvlWkDay:04 IntrvlMnthDay:01 IntrvlMnthDay:02 IntrvlMnthDay:03 IntrvlMnthDay:06 IntrvlMnthDay:12 IntrvlMnthDay:24 2. ReccuringPaymentAmount and FinalPaymentAmount must be the same as FirstPaymentAmount 3. RecurringPaymentDateTime must be the same as FirstPaymentDateTime 4. FinalPaymentDateTime is the date until the SO is valid
6	Domestic Standing Order	POST /domestic-standing-order GET /domestic-standing-order/{DomesticStandingOrderId}	Y	Supported frequency: IntrvlWkDay:01 IntrvlWkDay:02 IntrvlWkDay:04 IntrvlMnthDay:01 IntrvlMnthDay:02 IntrvlMnthDay:03 IntrvlMnthDay:06 IntrvlMnthDay:12 IntrvlMnthDay:24 2. ReccuringPaymentAmount and FinalPaymentAmount must be the same as FirstPaymentAmount 3. RecurringPaymentDateTime must be the same as FirstPaymentDateTime 4. FinalPaymentDateTime is the date until the SO is valid

Confirmation of Funds API

Swagger version	Confirmation of Funds API (v3.1.2)
Base URI	https://sandbox.matls.api.ob.zempler.tech /open-banking/v3.1/cbpii https://matls.api.ob.zempler.tech /open-banking/v3.1/cbpii
General variances to specification
Non-functional limitations

Area

Field

Available (Y/N)

Exception/Notes (inc details on classification codes, field limits, and field formats)

1

Funds Confirmation Consent

POST /funds-confirmation-consents

GET /funds-confirmation-consents/{ConsentId}

DELETE /funds-confirmation-consents/{ConsentId}

Y

2

Funds Confirmation

POST /funds-confirmations

Y

Open Data API

Swagger version
Base URI
General variances to specification
Non-functional limitations

Ref	Area	Field	Available (Y/N)	Exception/Notes (inc details on classification codes, field limits, and field formats)

ASPSP Documentation

Implementation Guide: Zempler Bank