why2 reasons
mandatedestination_not_allowed
op 0 pays GDFS6O4OAYDZPWA2MY7ZNMESIIF5AR3BFZ4ERWSII746CPK4DG445AJ7, which is not in the allowlist
counterpartycounterparty_denied
GDFS6O4OAYDZPWA2MY7ZNMESIIF5AR3BFZ4ERWSII746CPK4DG445AJ7 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
- aae3eaee170af20fc52e13697f82c80b6b15cba999e49b2026eb398a35950ff1
- request
- 10f7e63daf947bd4dc3080fc77b5fc1fff740c6ba976bdfe36cdc2f00e7aa8b2
- transaction
- 60227b88a04b03f2b4139f4defdec0deebaa6552913412cd813c8312c3a38a89computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38764
the chainentry 38764
- sealed to the entry before
- 0a05e151870734bf3fc8ff1b3a865c0b93717b476b7d46cc44fc4f0c5f2cae23
- this leaf
- c1f904cefe565f3428e903cf4e619168d8a26a2c0d3047d088aa8c298e2cb4b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QyZdMUmyuNFvBwyCvDJ03MON9yO3esCSidh4pfb/k03igxHukFsY3inuYBsQUKVl4IuRe7OeegtWYi2bAPX8Cg==