why2 reasons
mandatedestination_not_allowed
op 0 pays GBFNNRKFGBVOYBYYD5AD5VQ6INAV5ELMR3K6GFH3IB6TSSSDA3AZPUPN, which is not in the allowlist
counterpartycounterparty_denied
GBFNNRKFGBVOYBYYD5AD5VQ6INAV5ELMR3K6GFH3IB6TSSSDA3AZPUPN 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
- ed232ed25ed78938e1cecbbb0f0a3ab7ce3dfadbf01414704fb76ddfd07e274d
- request
- ddd0f8db2ba8b9cf7497652d7f8d8039e551495e0a922975d2ea58d891e25eb7
- transaction
- 93d016dca73d570b5b0ef53b82365446e4888edd7ddfb6ffebc38a9832c2cde7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1153
the chainentry 1153
- sealed to the entry before
- df1427353b8a5f23cafb815bcd7d0dd8955ffa2b5f1b71f29d697c12be13c710
- this leaf
- d447242adccee65c8e6fbf3ffed0f5b279fa03280eb155fdca00ef75db3b6372
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SB9JFIAwpGq9uKKYhUaX0rto73Ud4U6rtPVrU9Yjjr5/7dn/DNAEKujHMYKetqhpCFBNWSwuJcSWN2o1ToEpDg==