why2 reasons
mandatedestination_not_allowed
op 0 pays GBGTY2YAZ5YLUX6WH3KVMQV6O57MLYEYUHOPN2Q3GC5EQTBQX3BJPB4D, which is not in the allowlist
counterpartycounterparty_denied
GBGTY2YAZ5YLUX6WH3KVMQV6O57MLYEYUHOPN2Q3GC5EQTBQX3BJPB4D 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
- 7ad11a90c61daab2c71ac072407fb38425093138b13111df4ae599e2aea4a58e
- request
- e34bd6e78717a9fcd45cc91ab965814fed2d312db9bce2c0ad411a38cf045278
- transaction
- 4fba99973f140b54252e9d0a3f0e92d150a81f36da084a5bf607dfe7052f0f99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39360
the chainentry 39360
- sealed to the entry before
- 4a3584b2819fdc40890d59ebef8abf59d06da47e56dcf8651ded79cb3357c45b
- this leaf
- 7daadcd10d0814bb37960cdb6184d3f0d62b4faade08d8be5444be1409b39ef7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x/Ftc2Z45HbNuz2AQU7lE30AfOP+Hc0d7MHk7z13zYC6U4rhHUIlJPluMcxwFQGEJ8usLoCXM74f3CAiRh8uBg==