why2 reasons
mandatedestination_not_allowed
op 0 pays GBCDI4JQFAXX6A6SGMW54T5CQXN2LS35BDUKF2DBFRX4CUXGDRD5CYHX, which is not in the allowlist
counterpartycounterparty_denied
GBCDI4JQFAXX6A6SGMW54T5CQXN2LS35BDUKF2DBFRX4CUXGDRD5CYHX 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
- 66fd11eeb162273bc853409b26ec36824c22af4820567f0841b4fdd3eaebf64f
- request
- 72fe2c384cc7856d3f9eb07fff1cb9953607f7aec8a3b8805001a4cf56ae37c7
- transaction
- 69f6f464a63180f732d585738e0c04d760faadf498db3c98f6beb1132e92a1bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70715
the chainentry 70715
- sealed to the entry before
- 32e305610a7ad9b0888682f36ba2ea0db5f56d740042c6f998079dc77bdf1315
- this leaf
- fcb3d264bcaf35639860d482eefb3dcf03218edc8dff517785bbe8a9c522d5da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kGws2SEVnKfznfJTIhC44uooXgxFOuEVaF9rGI8ZIPzltr4U4nIONLxyQaFrNTgI2x18ArDNarONYoclcFsMCQ==