why2 reasons
mandatedestination_not_allowed
op 0 pays GBKHXA5N4M3RIYEK4NC4JRSB3JLXMDAGGGWMQ5SVOKTKEMTQ7IH26R5D, which is not in the allowlist
counterpartycounterparty_denied
GBKHXA5N4M3RIYEK4NC4JRSB3JLXMDAGGGWMQ5SVOKTKEMTQ7IH26R5D 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
- 4a843fec3c2f422333dadb4ffdb887d8ecd26b9ddc9740f5f75105836991ae1d
- request
- 7f06bd812f3935ce0231bff4c887282d68b34c2b46a381909b58b8d8be3d6984
- transaction
- 62af27d111d384f7ce960b892bca1e332fc5d895e34806e7f0937ae0c20f28f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48561
the chainentry 48561
- sealed to the entry before
- 6493dc19ad587b63e92093b4bb219addf7d06627624f8086cea5926acce0c8a8
- this leaf
- 3fb83f6e801d27f7ab2d956525c84a1314159404a0a35bdd194ddf760977ad67
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uvhAmNbu9+RxK//YDk9PwgpwyWFvQ7XUHYo5ia6rjQi4GyECQeVNMLsGgTgvMcc+X/b0hbaKrpPeuJRxFsCkCA==