why2 reasons
mandatedestination_not_allowed
op 0 pays GBISVUKEJGVAIJEUCYHF4OY36HCCCLMTUG3L77MAAHZ6Z4RQSONCMVZD, which is not in the allowlist
counterpartycounterparty_denied
GBISVUKEJGVAIJEUCYHF4OY36HCCCLMTUG3L77MAAHZ6Z4RQSONCMVZD 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
- c9b3e9f007260873c5a7682b2ae9ef6f8a396d5c20e59035ca45b54eda650288
- request
- 7110aa7f89a169124662e1dd87ac3a6e576b2dc0f1f4496e50b0cf493968e313
- transaction
- 9d18a429be019077e65a11c486cac3e61434fa96df7456094fb741a02950a3e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58903
the chainentry 58903
- sealed to the entry before
- 63114e311fc8026009b75779c3538085f7f7a3130e549e264b8c9588aade59ed
- this leaf
- 698426054e99aab6731ed04d45badc21779b4cf3691aa388456495ed68907bbe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ONBT4LLrm9jPkmYtQoCvNcb1dxT0zxQrB3lXMA1hhfCNeeJHACNSrHnXymh/HqDkx7QJe/iGXrAc1iHNfJnACQ==