why2 reasons
mandatedestination_not_allowed
op 0 pays GBR6TO5JPA6A4O2OM4R7VIZJY3FUXJIWQSTC6WG27ESKEY6QBB4UUKGR, which is not in the allowlist
counterpartycounterparty_denied
GBR6TO5JPA6A4O2OM4R7VIZJY3FUXJIWQSTC6WG27ESKEY6QBB4UUKGR 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
- ae6101272e73dc0a23581ce5af655869f468c97f89b39cc0b33af31c13c0e47c
- request
- 9721e128c9807e3b9a2cfe721fb4a8749194aabf54e240908fc17235418d6bc0
- transaction
- b50cdc0f7d772d0bcb27da4e5cf05d31861c2f1ad513517083d6169295d7d7cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8039
the chainentry 8039
- sealed to the entry before
- 2c672e97a103ca0741c41618a6492270835d5627ff46cdde68014e41ebe93b5f
- this leaf
- e8a44c135ddcfb47bc38a2f11a7d5bb5396ccc7611ba577b5fea196bd9fec28b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IqmhnqomhqqxdTrZ+GaCt71GypDV0GY5hSpZHdWZghR9zggcvDHC2wAVn27uMmS3PXO0GNRk7mj/AkPdQyAJCg==