why2 reasons
mandatedestination_not_allowed
op 0 pays GD4PJDEISKECN3WQADKWHHEIKNR75J5D5ELW2YI42PSFOO3YFYGQMG2X, which is not in the allowlist
counterpartycounterparty_denied
GD4PJDEISKECN3WQADKWHHEIKNR75J5D5ELW2YI42PSFOO3YFYGQMG2X 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
- 06f9ea59e75a5f5dfd493cc86dabaaf14b471eadde961dec2ac6b278e61a8e51
- request
- 09b4e4206c27c937502d31e423165864da8b00bafe88344a3b8291cbcbac46a6
- transaction
- c75efa469270a2921e0bc06c2aa682ca1b1cb8c1b480174edd36bdf9d6a43195computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1296
the chainentry 1296
- sealed to the entry before
- 2eb6f0e9a77659b736c1124873ec4bfde508102d74fad2a0db4caf8c28ca9342
- this leaf
- 597f752d05b3afccedb46827668dee428e8cb406e3f055da7eb6a1dbb1fed477
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QrbphF7IEoe4PCtVst3Z2MqmfH793bcmpHSmO7+uh4u6UrbFa4D8ZR7s/bnLgejOxtEPwj1bgV2kakVxLlTdBA==