why2 reasons
mandatedestination_not_allowed
op 0 pays GDYFAKXQWX2K4ZEYTKNHVO45SC7464FCQKEO6X3LZ3PO2X5ZTCDHGQME, which is not in the allowlist
counterpartycounterparty_denied
GDYFAKXQWX2K4ZEYTKNHVO45SC7464FCQKEO6X3LZ3PO2X5ZTCDHGQME 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
- 58f7410711c213fc92070b82a0c7525b0cd8aa1f9aa5f0b69a9356ee02290bfe
- request
- eaf8f0563178a631c7a2e4732d034bdaeddcd3a21aae90b86fd0adefaca2f6e3
- transaction
- e6889c2023675ca7cd5889d84df575a01a3839249d963305a4424924afc1c05ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54880
the chainentry 54880
- sealed to the entry before
- 24d168451ca66a781e7ada45848c78bb9723dd524c1b495c1ea7e4b559f05040
- this leaf
- dd82a42bd0440d997109498ccb45b06babfa5e4c5d35f8d6ddce6da02e15c688
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tCwukkrqmswi72QGtQnIApBqVvys0H+WLauDs/YRGi52b2vwy/RmlOAft1UB7HM3XFUhaGyWngifY67L6rgmBA==