why2 reasons
mandatedestination_not_allowed
op 0 pays GD3TAHU4Q2FYWR274A3FSZLTUX6JYP2563O44QPYBF7WJGAFY4GF62UA, which is not in the allowlist
counterpartycounterparty_denied
GD3TAHU4Q2FYWR274A3FSZLTUX6JYP2563O44QPYBF7WJGAFY4GF62UA 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
- ec6e9ca1ae4e8a6fd833515a63d8ef8aeeb81cf78ef82de42721139377e80b75
- request
- 3ec29945906dc9b13ea57da834159fc70cba9c2d76320acc2073cc71c275fde4
- transaction
- 52820507467ee855841bd79c6c61a453b4ee63a16dcb37a33a19846c21796affcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77595
the chainentry 77595
- sealed to the entry before
- d20b5bb14f7769870603c7ada086180499fad48e8be621e7e01478a8835a88fb
- this leaf
- a5a772b14d8840d8a7eae2fc6ad6e125aab05b7e61943f8c4a7c48659bc46b44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g1AWjhU5MXy8Apt4KBZJ2+DnDfrYZ/Zc0dHx6oOYNL/HTDBuf32RGxx/KVrC0Uka+YvgYtAYZudL8bRhRbNFCw==