##  [Deutsche Bank Developer Portal (2026)](/nominees/2026/deutsche-bank-portal) 

 ![Screenshot of Deutsche Bank Developer Portal Home page header](/sites/default/files/styles/nominees_image/public/2026-10/Screenshot%202026-10-29%20at%208.58.32.png?itok=Zp8lsJQs)

 

 

Owner

Deutsche Bank Group



 

 

 [ Visit the portal ](http://developer.db.com) 

 

 

## NOMINEE OVERVIEW

The Deutsche Bank Developer Portal provides a central place for developers, partners and businesses to discover, explore and integrate Deutsche Bank APIs. Originally conceived primarily for third parties building services for bank customers, the portal has evolved to support new use cases, including business customers connecting their own applications directly to their Deutsche Bank banking relationship.

## NOMINATION RATIONALE

### 1) BEST REIMAGINED ONBOARDING EXPERIENCE IN A DEVELOPER PORTAL

**Why is this category a strong match?**

For us, reimagining onboarding did not mean adding another tutorial or making an existing process a few steps shorter. It meant questioning whether some customers should have to follow that process at all.

Our original Developer Portal assumed two different roles: developer and bank customer. db Smart Access introduced a new one: the customer-developer. An SME connecting its own ERP or accounting environment to its own Deutsche Bank business account is fundamentally different from a fintech accessing a customer's account to provide a third-party service. Yet historically, both followed largely the same onboarding logic. We changed that. The new experience recognises both the relationship and the use case.

For read-only access, existing business customers can connect their application to their established Deutsche Bank customer relationship. Once that relationship has been verified, Client Credentials allow the application to consume the corresponding banking information without imposing a recurring third-party consent journey.

Where the customer wants to move beyond reading data and initiate payments or direct debits, the Code Grant journey remains.

This distinction is deliberate. We did not simplify onboarding by removing safeguards. We simplified it by applying complexity only where the use case requires it.

  
**In what ways does your portal shine in this category?**

We redesigned the path from discovery to productive API use around four simple stages:

**Discover**  
Start with the business need, not the banking infrastructure.  
SMEs typically arrive with a straightforward objective: connect their Deutsche Bank account to their own ERP, accounting system or internal application. They should not first have to understand third-party roles, OAuth grant types or traditional banking connectivity models. The journey therefore starts with what customers want to achieve: integrating their own banking relationship into their own digital processes.

**Try**  
Understand and explore before connecting the live banking relationship.  
The Developer Portal gives customers an environment in which to understand the available APIs and prepare their integration before connecting their own banking relationship. This separates exploration from production access and lets developers establish whether and how the APIs fit their particular use case.  
The objective is to move customers from: “Could this work for us?” to: “We know how to integrate it.”

**Connect**  
Use the simplest appropriate journey.  
This is where the experience has fundamentally changed. Instead of pushing every SME into the same onboarding model, db Smart Access differentiates according to what the application needs to do. For read-only use cases, the customer's application can be connected to its existing Deutsche Bank relationship and authenticate using Client Credentials.

For transactional use cases, including payment initiation and direct debits, the customer follows the Code Grant route with the corresponding authorization. This creates two deliberate paths rather than one compromise:

- Read → first-party connection → Client Credentials
- Transact → authorization required → Code Grant

For the customer, however, the underlying principle remains simple: the onboarding journey follows the use case.

**Use**  
Make banking part of the customer's own digital infrastructure.  
Once connected, customers can integrate available Deutsche Bank banking capabilities into their own software and processes. They do not have to adopt a prescribed ERP, accounting application or external software solution simply to consume the API. Instead, they determine how banking information and services become part of their own IT environment.

And this changes what successful onboarding means. The destination is no longer simply: “API credentials issued.” It is: “My own application is connected to my existing banking relationship and I can use the banking capabilities appropriate for my use case.”



 

 

2026