why2 reasons
mandatedestination_not_allowed
op 0 pays GB43SS3PSZPYNZGW7BQ5CUCGA2FUP5WMEY3DN7YFT57646PSPYFYTJQH, which is not in the allowlist
counterpartycounterparty_denied
GB43SS3PSZPYNZGW7BQ5CUCGA2FUP5WMEY3DN7YFT57646PSPYFYTJQH 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
- af3c7f56adf92a113c07f285ae1f87c534e939f68be63f232a08e09c9b224e8e
- request
- 1361e0a3e80d58157bbb16be22d11a0f74ae6862c35aafea52a75363a831f2e6
- transaction
- b1fd2c233865dda30e5a6e12cdb835095012a56fdbf046729e459d273e5df825computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1781
the chainentry 1781
- sealed to the entry before
- ee654b00b90c8f9312a77d5e5f69aa2d89bfeb4a4c7885aac6e429e05656d3f3
- this leaf
- 2ed8d43d7eeb0223ddc0adf6bdc6c821ac68f31425c041cd1e78b928e9ddd805
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u2FnFxzSYTYjTgxEwtOHM0aYmWh3unSQS81Hh+4HhZlnzwVm5Sd2CW1mCtOxdaBrf2XbztRP1BmYMfWMEhgiCg==