why2 reasons
mandatedestination_not_allowed
op 0 pays GB7NN6V6Y5BFV5G3DYFYQ2P5L2RTIZA5QG74RF34XXEFDBXLPYQDCZEC, which is not in the allowlist
counterpartycounterparty_denied
GB7NN6V6Y5BFV5G3DYFYQ2P5L2RTIZA5QG74RF34XXEFDBXLPYQDCZEC 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
- e59efde1a8483b48ae634b3df883a20b74337dc6f52da8825bbb7e59e0494270
- request
- c1dd073d2dcdfc03063ea28758fc6d509f7d3a6edc10ad7ac0e31ddfce967d48
- transaction
- 0fca4319f2124334a54be7d10c9aad7ec3705ce75eb1223c90a6d339c252a216computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22034
the chainentry 22034
- sealed to the entry before
- 13bdb4cfa986755be7bac2c1ac5bf6c84f98c9e6320f5ec7158e086fe6e1885d
- this leaf
- 600c92703454d49e09fc4a2c7206443b6f0753d6d00bf20e946d124001587498
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DCz/Tfq5MmuJfYKfthok9Y7nS4pC0FbnIMsbvxVo929w23fi1Uoe/EK9KDBhmyIlVIt+5PFTSxnv9eNw7XCvBA==