Deutsche Bank
Configure Deutsche Bank card and SEPA Direct Debit payments with Hyperswitch.
Deutsche Bank supports card acquisition and SEPA Direct Debit through Hyperswitch. Card payments require 3DS, while SEPA Direct Debit supports mandate-based payments. Refund and capture options are listed by payment route below.
Status and capabilities
Integration status: sandbox
Category: bank acquirer
Webhook flows: None declared in code
bank debit
SEPA Direct Debit
supported
supported
automatic, manual, sequential automatic
not applicable
-
-
-
card
Credit Card
not supported
supported
automatic, manual, sequential automatic
required
Mastercard, Visa
-
-
card
Debit Card
not supported
supported
automatic, manual, sequential automatic
required
Mastercard, Visa
-
-
Authentication
Provide the Client ID, Merchant ID, and Client Key shown in the connector form. The labels come from deutschebank.connector_auth.SignatureKey, and DeutschebankAuthType::try_from() maps all three values.
They are not used the same way. The Client ID and Client Key obtain a bearer token before the first payment: Hyperswitch posts a form to /security/v1/token with grant_type=client_credentials and scope=ftx, sending the Client ID as client_id. The Client Key is never sent directly — it is the HMAC-SHA256 key over the client ID, the current HTTP date and a random string, and the base64 signature travels as client_secret with a V1: prefix (token request). A wrong Client ID or Client Key fails at this step.
Every later request carries the fetched token in the Authorization: Bearer header, together with the Merchant ID in the Merchant-ID header (build_headers and get_auth_header). The Merchant ID is not part of the token exchange, so a wrong value surfaces on the payment or refund request instead.
Before you start
Request the Client ID, Merchant ID, and Client Key for the DirectPOS REST API (merch.directpos.de; testmerch.directpos.de in the sandbox) from Deutsche Bank. Once you have them, follow Activate a connector on Hyperswitch to enter them in the connector form, then return here for connector behavior. Deutsche Bank appears in the control center payment-processor list (connectorList).
Webhooks
Deutsche Bank webhooks are not supported. The webhook methods return WebhooksNotImplemented; use payment sync for payment status and refund sync for refund status. See IncomingWebhook for Deutschebank, ConnectorIntegration<PSync>, and ConnectorIntegration<RSync>.
Source reference
Authentication and webhook behavior on this page is tied to Hyperswitch 7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8. See Deutsche Bank connector source and Deutsche Bank transformers.
Last updated
Was this helpful?

