why2 reasons
mandatedestination_not_allowed
op 0 pays GDAFYA4FSR42DOF6KWNFTPIRJQLB3YC5YICXAXDEJKDODZS5C4P73S4T, which is not in the allowlist
counterpartycounterparty_denied
GDAFYA4FSR42DOF6KWNFTPIRJQLB3YC5YICXAXDEJKDODZS5C4P73S4T 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
- 47a6d1392f9321345fc63195baf3d86ed7cb3e6a3caf6bc0ee42a9ba5468a7af
- request
- b2979f3e4bba9ff513545220f5eeaf62d8715e340709c8513ca0389a2db97519
- transaction
- 22824411f9bc8bfe9d2d5f568174649245d94f9ef115ed10d1ef50bc8116cdd0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22086
the chainentry 22086
- sealed to the entry before
- be3915eea7de3bce7e215cfb528cb20fa0692859682d9486b4e632840d9d0ef8
- this leaf
- a1fd261e7f779ffaf80ad717a32e67141a595672212a8237c583f6e3e101a092
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QPEbPZNYSPW6UI/hxX4EG6hYndtMmhVuor1Qvs3AMGE3kFDZsaE9vTOe6CkPDMn2njrCarb8cfWFPxR3TAGmBA==