why2 reasons
mandatedestination_not_allowed
op 0 pays GDP3OMOHMIPDHKIXKOIRLJGLNNGKRXK3OKJR32PYSOJVC3ZU2NVOQPJW, which is not in the allowlist
counterpartycounterparty_denied
GDP3OMOHMIPDHKIXKOIRLJGLNNGKRXK3OKJR32PYSOJVC3ZU2NVOQPJW is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- ce82bdd79b768bc5d56babaea3e2db689bd8e788137a5ae69a730228bb4770a5
- request
- ade814cda3b5bad8a0bf097ae09f96d460dba65ee220ededb8bd041bdaa36427
- transaction
- 78adca0d21c6fffe2fa6a8f21221e93d3579df7a6a6b226d4d8fae6216316aa3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28809
the chainentry 28809
- sealed to the entry before
- 98f0b9a17e67277648e624726842b218a97b6a30cfaa6718af5de5f19ba39b1e
- this leaf
- b7f5c4356869f0691a044b96e56e4a1f9ca114cd9c3e92f784f99657081f1b16
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D6C3NT4q1X2dqY9/xWGqf8U/26MHwzQw9TexpRMcDCzqBKPexp2KFGGnA4lG36RK9ISILaifiz9Gc9jK9QvdCw==