why2 reasons
mandatedestination_not_allowed
op 0 pays GBCZ5RMTRX6FN2HXL347HRXE3SHLZITPN2QIX7VQKURVH3UHZG7IYTRV, which is not in the allowlist
counterpartycounterparty_denied
GBCZ5RMTRX6FN2HXL347HRXE3SHLZITPN2QIX7VQKURVH3UHZG7IYTRV 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
- 63f6f6576796e8f74743f970a9f891f2a6c01710dfc0f843be80b59f381e058d
- request
- 6b17f7483e875108a7125c00bbc4a8dbf5466a9fceec2c45d3a0dd54b412768d
- transaction
- 1d2ed6d335a7198800845b726089b54e9c8692020517bd9d93ace6650c19ab47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24708
the chainentry 24708
- sealed to the entry before
- f35972c55ae6dbb8e9b30f78839dfd92447ebc8cfee04d14b96902e6c58cfa04
- this leaf
- 273bf7057a8549c6ceb233eb8598ce500047fcf06772b30f8a03ce898a758e5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6ATTH8GM3vY/si+nmzrd0qWEY3IMCdFgr1AMHoFKIH4sHrFtDnVeoKlLrOArX+BnU/JOyfC8LsRXggyVs8xnAg==