why2 reasons
mandatedestination_not_allowed
op 0 pays GBIBRXELM4CD4LHK5RTYTMKHJBO4D7CZXGLGLGPR62J3XTKNHYXCBQWE, which is not in the allowlist
counterpartycounterparty_denied
GBIBRXELM4CD4LHK5RTYTMKHJBO4D7CZXGLGLGPR62J3XTKNHYXCBQWE 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
- f8f00a6c1feac3ec4039aed663190b0afe9cd9c27bc6d782a6e0ff531a8ee968
- request
- 5c75aca0a9906292a6843d104b1b7f2dd4ad2c3a357e7a6975d52b7e9fa8c005
- transaction
- 59623b6c66a3d30f9681cab58a8b506af54636c57e08433ca0e2063ffd6b1da1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51099
the chainentry 51099
- sealed to the entry before
- 08be81653c3f2823dbd2b9ad03bb1c24acf7a2853171228acb41bb40f07ad15c
- this leaf
- ae43db61af109803fb8625637ff203c9896217497672d60eb74f39e046136125
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mKBa4UylKelM2g2gOFhxf3dD+ZfXx/+mCiL03xg1TRdPRarXu4HQribtpXTJoHKQ6YEkxxo9qS2IfxCMVqTIAQ==