why2 reasons
mandatedestination_not_allowed
op 0 pays GD7ISBPWH6MZXYT72FXWJYIP3R65D6J2XWDYK3PI4H5QFFBY5KFGZ7XR, which is not in the allowlist
counterpartycounterparty_denied
GD7ISBPWH6MZXYT72FXWJYIP3R65D6J2XWDYK3PI4H5QFFBY5KFGZ7XR 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
- 63e0a25624fe35d52de4148aa50758ee4b895ae2a266a31a38ebb7affa0dbe8c
- request
- 5f034f45c7ad393b993898fcde04a7b02b57a5ed74ca5acd7103b41a08adf0bc
- transaction
- 68980a5989dafe8994175180a5938b8b249ddf14c5fa5ce278d50b82725783a8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 262
the chainentry 262
- sealed to the entry before
- b64a5a3324babbc8f559e49799368d1829935b742335e6625e9756949fd86864
- this leaf
- 86e2e10e6155c70d8be494d7b456aedb0951811669ac5081153f8877f0610f39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P1GbL5kzEVNOKm8pkE0Dg3NlbfWSXQZCpaqNKZusOOTF5acAj3HzQNhX+Vo+SqVbyitG5zzPbc1rixMGIptMCw==