why2 reasons
mandatedestination_not_allowed
op 0 pays GDISAO7CUJPP6A2364WFYPUZG5J7VL2DNNCQX6R57IWFYJPPP2UDLK4R, which is not in the allowlist
counterpartycounterparty_denied
GDISAO7CUJPP6A2364WFYPUZG5J7VL2DNNCQX6R57IWFYJPPP2UDLK4R 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
- 473c37a2a59195ebab75baddc18e5cf2f4682b8457642c533a79a9f491293a07
- request
- d4edeb45b6b6848102af4a659a75eeaa137f78db9a05023fdd35d3ae760cbbda
- transaction
- d637d41eaa1d8706d920dfdba8118d6f730814d78b17a9d16307cd04b2906092computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44374
the chainentry 44374
- sealed to the entry before
- 6d3891c007330348d5ce97cca108b2f2ca6f3a332cf46ac7894c7903a2a6916c
- this leaf
- 33e7401d46699256509c7ede613a91e63b2ac4e0c89fbd5f3b35303284c7089f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +OOKWV7Qr3ctGsXxD4BQNJfJPMtF0VZG2h3fDATjmsXWJ+jc/uJ99EuHAcak9CR6nQTK68Hs9e1p6CuCMAQXBA==