why2 reasons
mandatedestination_not_allowed
op 0 pays GB5HZO2SRXUQQPVRAB3O3UIIZC3O72LRF3T7LE5PEDOAOMLPG2RDXN2I, which is not in the allowlist
counterpartycounterparty_denied
GB5HZO2SRXUQQPVRAB3O3UIIZC3O72LRF3T7LE5PEDOAOMLPG2RDXN2I 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
- 8f658bfc0ba1d00b09cf561dc27da2c515d0f3cedea65efde8bd95104d6f0a56
- request
- 4cc3ac53a29c1094936121a04a815cc90ca770f87c82ee294b238759d48c8375
- transaction
- e39851a74c0879f5d0258b0212e8b4a02138325ebc8c73a158e62ebe6cf4f0f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77377
the chainentry 77377
- sealed to the entry before
- 2e989438a8b929df99996b1041c6d404e2116500558b62d267212fd184b332e4
- this leaf
- 9d53b6384b37a6ba3d634b62b2337f7d9ad06fc11bf902602d23ca586c4d736e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zD2RGZbEj7+gnKll08fb6Cvw2wEULKNvDJrNBqGJXtS+ha0fqgcQ7cj3OCY+ni1B0FZTwauAywQEXYiwfUSiAw==