why2 reasons
mandatedestination_not_allowed
op 0 pays GBJHUI23LN2CXIGYWRV6EO3B6X4OKFBD4HMWR3AUHACE3EAKL26RUL5L, which is not in the allowlist
counterpartycounterparty_denied
GBJHUI23LN2CXIGYWRV6EO3B6X4OKFBD4HMWR3AUHACE3EAKL26RUL5L 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
- face37ec509e5df56c72e90076dd2f54d08be12190b855727b4da61942ec6dfc
- request
- d077eed634826583ca1eef5f46622098d4232bf85357f63a0a75b71724f5f1f5
- transaction
- 1ad6e777cba257615297d630987f510ce8bd1d2298976bea8a45f1d5cba23a4bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2396
the chainentry 2396
- sealed to the entry before
- d961c5c806292979a0b1f53cccac9e06e2d725ba03bdcd2d783d73f1a4d0aba1
- this leaf
- 39cf83e97b9a364b3a020bdcfe2c7b6312743ea7e0776be7dca549c27271d8ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a+XLyAUgIdao7wvF01MQKcmZN4osTxVMx6/+goeE3Fm5+YE5ykTXy4YCe+iuI/0npoYhR8VJfufWLWTDsjuKCw==