why2 reasons
mandatedestination_not_allowed
op 0 pays GB7NS5R4A5BUV3JBYRRFTP7M7NQJY6ADYZ2JFX2ZRWHOYVLXYLAR4KQK, which is not in the allowlist
counterpartycounterparty_denied
GB7NS5R4A5BUV3JBYRRFTP7M7NQJY6ADYZ2JFX2ZRWHOYVLXYLAR4KQK 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
- 66b736a9ca890d423c6e7113da95f8b13367e038738bad3e886c3f9c4d32cb87
- request
- 57c60415db8a69f40c34eecafdd83e5e6e4636df896a5f61503385cb1b6430c7
- transaction
- 057be4031d6fec561562884d2347a2528796d49726cb616353e926c2a806451dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 217
the chainentry 217
- sealed to the entry before
- 6bf09fbe9f4cd0415733178b0697c291e5a749b679735ff1290377c4562895a8
- this leaf
- 352353edd0df17590783db0f2ace538e129c498a5026977072b7477846a7af82
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- htMhop2NKUEEYodRhYlgTa9VGgF35X3XGLRgdPZodFcIBjvsmkTSWv1cyubxQw91GOZlRFX8OeLLY0brpy71DA==