why2 reasons
mandatedestination_not_allowed
op 0 pays GARMDQEEH4H7EVICHVTJBX23M3ESNP3DNYNY4BWUDCE6JG4SWTMAXNAL, which is not in the allowlist
counterpartycounterparty_denied
GARMDQEEH4H7EVICHVTJBX23M3ESNP3DNYNY4BWUDCE6JG4SWTMAXNAL 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
- b6bf0c4c11151101c74f3cd7e9ad024fa46a24a82694e26c3a8ded5fe0af5d83
- request
- 4f572450371c810cf11a898b6f5441740e115765eb8c14970056add06977b6e9
- transaction
- 5c85969f3be951b7fcbde13e04a9ea8ea01819533e463f55cc163dc6589a9c0acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 462
the chainentry 462
- sealed to the entry before
- 971bf77ecc679ebff4d98f2b501c1f83562ce577c51037fc48724c40ddd36ca9
- this leaf
- e6ad1d2347ce481b9509457a649c33212669e1a60e7f115c5295623893570f84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 20D35D1lNc48We0n43Zxo714taKiwPrttfjzOV+DX5ZFQfjaWCK7jIljZi9MOsPUEt+UxMvD7QBadsaR8ACpDg==