why2 reasons
mandatedestination_not_allowed
op 0 pays GBPH2LJTZ5ETYVN53CDZK42536H4IXGQCR2PPANG4KOWN3IUNSWTMZZN, which is not in the allowlist
counterpartycounterparty_denied
GBPH2LJTZ5ETYVN53CDZK42536H4IXGQCR2PPANG4KOWN3IUNSWTMZZN 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
- ced3aa9eba5d88cfee35121c7efd11651ba7937c4b4bbb37e67cce8fc4769d3e
- request
- 8c7dd4cf7383abd45a7f5b4b72fcf6d969aa7f5253a6ad0969e253919dc23d08
- transaction
- f8efcfbb806426661226ad2c8563c6cef3f1ddebfe1ea75573f39cae2c6c6c12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71833
the chainentry 71833
- sealed to the entry before
- 246ba22071bf866cad89c994e5b1f3dc1c7c1da761ffb00eeb91a6bcc3abd72e
- this leaf
- 0f4427823f60b8470fb8dd3d2f89c9283164d1ef765f8cb0a5a1bf373a413380
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ahvvTM3zREp2skLmLXGWIMVbY+tyVj6wo51W59x3KdjTLpMJ4B+yccsJlplWiZaM/97JtdWdLzKsvCxzA2E+BA==