My Oracle Support Banner

Error: Account Number not mapped to Party, Received in Response When Trying to Get Account Numbers Mapped With Party ID (Doc ID 2752066.1)

Last updated on MARCH 02, 2021

Applies to:

Oracle Banking APIs - Version 20.1.0.0.0 to 20.1.0.0.0 [Release 20]
Information in this document applies to any platform.

Symptoms

When attempting to call the below API, error is received in the response and log file.

API:
digx-auth/ext/v1/accounts

Response:
{"result":"SUCCESSFUL","message":{"title":"Account Number not mapped to Party","detail":"","code":"DIGX_OB_0017","type":"ERROR"}},

ERROR
-----------------------
Account Number not mapped to Party
400 Bad Request

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Call the accounts API by passing the generated consent id.
2. Login with the Party ID using the returned URL.
3. No account is available mapped to this Party ID.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.