בית › Ohmyfin עונה › Why does the Deutsche Bank tracker (corporates.db.com) show no results for my UETR?
תשובת Ohmyfin למטה (באנגלית).
Deutsche Bank's public corporates.db.com payment tracker only retains records for about 7 days after the last status update, drops records once the payment moves to a final state (ACSC/ACCC/RJCT) or is recalled, and goes offline during scheduled maintenance windows (typically 22:00-02:00 CET). The payment still exists in SWIFT — DB just stops showing it on the public endpoint.
The corporates.db.com tracker is a public, no-login portal — Deutsche Bank intentionally limits how much data it exposes. The most common reasons a previously-visible UETR returns 'no results' a few hours or days later:
Retention window: DB's public tracker keeps records for roughly 7 days after the last GPI status event. After that the record drops off the public endpoint. The data remains in DB's internal systems and in the SWIFT GPI network — it just isn't queryable on the public page.
Final state purge: when a payment becomes ACSC (settlement completed) or ACCC (credited to beneficiary) or RJCT (rejected), some bank-side trackers de-list it from active lookup.
Recall / compliance hold: if a camt.056 recall arrives or the payment is moved into a sanctions / fraud investigation queue, DB hides it from public lookup as a privacy measure.
Maintenance window: DB deploys to corporates.db.com regularly, typically 22:00-02:00 CET on weeknights. During the window the page loads but the data layer returns empty.
Best workaround: use Ohmyfin instead. Our backend retains tracking history longer than most bank-side public trackers and works for payments that have already moved out of the bank's active window.