why2 reasons
mandatedestination_not_allowed
op 0 pays GDQN5VKUXRKPLG2JXMAJPQM43SLQOG54JDLS4AR7PXYE5TRF6G7QUD3U, which is not in the allowlist
counterpartycounterparty_denied
GDQN5VKUXRKPLG2JXMAJPQM43SLQOG54JDLS4AR7PXYE5TRF6G7QUD3U 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
- 622fd564f121c90c82ce96615aeba8e6eee914edfd71e009486a476cf29805e3
- request
- ea082fd661ad18b14ac23f481ec5bf528bc4f2c0ccbe48dcf936affbf4b9543f
- transaction
- ebd8ad3ff0c2f678e7654709d7ca26b4e25b6e1a5fd56c3a1693b951b17b9b87computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51839
the chainentry 51839
- sealed to the entry before
- 862dfbb87b0a3a97dcb3b404462e7b4a84586a894550e7ca6ade257cbaf43ac0
- this leaf
- bad0b533285f713426bf1f91a0675d4810937ef204f0df437b02fd1680926ca7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wGnVbtV9E2I4x1yC4Ec1uvaj+st0zZT6CEo0wq2E/IwSEfMIcNgNb1T+umurU+U/+D1yKgxyIPLGyyURPyClAA==