why2 reasons
mandatedestination_not_allowed
op 0 pays GA5RTME3ZAYRPWW6Q3GTNR5QHW6XPQKD5NGYAY6VMINHREWYM36KD4T4, which is not in the allowlist
counterpartycounterparty_denied
GA5RTME3ZAYRPWW6Q3GTNR5QHW6XPQKD5NGYAY6VMINHREWYM36KD4T4 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
- ab3786614b8b0fb882587816b5db9713a93109967fd8ef235ae440e0e05c797e
- request
- af425991eecf2455590bba6f828a5a96aa201a5f43846fc72a53ded89bc24e5b
- transaction
- e6c8e4e17abb7eb05ee8ffc886cb457c4e5775795b14a8bdec9468ef9acdd62fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74222
the chainentry 74222
- sealed to the entry before
- 271160034faebb78a5ea4fc215fb42e1d839aef324d12e6a5e7d491d71a8607e
- this leaf
- b357880974182e9f59d506cb3b90366becc31fae24766bccac2c50b80fb5cb45
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zitOyMIMHRFc552rpJxV0DLZUdt3bdvw/ofd8APFYhA3PxFJtJ0TS7ZHxKW3/8xOmHhVPDvKcxVZvZE4zNDYBg==