why2 reasons
mandatedestination_not_allowed
op 0 pays GB4FJ4WW74MCDA55Y7EZUJYXCKRGH66WX7H2TYI3ADBHRQHBQCTCHRH3, which is not in the allowlist
counterpartycounterparty_denied
GB4FJ4WW74MCDA55Y7EZUJYXCKRGH66WX7H2TYI3ADBHRQHBQCTCHRH3 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
- 71782be713c9f8b638989abd7affeff3f2adbb6b8ddf7ef9e72a73d9bbf80aba
- request
- faa36bf13b93de7c3a3294a509f6ef0cbc7d1f3811d3004323fdcc7f1fb16cf7
- transaction
- 896e1eeeab4059da8c01fac7b82694534208c25bed012f0abb6d0a89ed4ed071computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1163
the chainentry 1163
- sealed to the entry before
- b9d31d686a30e4237b0aff794579ec04d4aefabed8606ca09b0f40cbdca1cc01
- this leaf
- cdc7938a506f6315ea61abede297967779794028ad695dc13bce7b8b188cadd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WiL3qvaLMeNiZ2aB6sBzsdJeevUeouf1axAbbEd2yvmZZ4vD2NcyUEE3hMIFwN2NmBwbHiWdSSgmtLfA1fyZDQ==