why2 reasons
mandatedestination_not_allowed
op 0 pays GBPLWFN2B5EBNKIJG5L5Z4AQ4YLVYYMELHDXW6VJIEJ7LJE3ZYGJHERR, which is not in the allowlist
counterpartycounterparty_denied
GBPLWFN2B5EBNKIJG5L5Z4AQ4YLVYYMELHDXW6VJIEJ7LJE3ZYGJHERR 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
- ed586dba281977229432e7a02bd21444cef06eaf6f23968f212de7723808bf7f
- request
- 71f1aa235cb3d3dcc2b13dc85575883f672d58b4c06dcfa1428221cd2b38ab5e
- transaction
- a73055a0082618c845a58a1a02a7b5e0967c04693d5469808e68c0721d27777dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1336
the chainentry 1336
- sealed to the entry before
- 762a23a6bed1148a55deaf28952d0bb7eebdbdee35aef95f4655fc6e7b4983ef
- this leaf
- 5ef0c2f2ce4ec0438bbdff5f664d109d9b4a028fa8856a91b1fe88fff03a51dc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mN2tdchtrXtKpvtGiQXIjeGG9XOshP2PLo9k2ltYi8cep9l7WCyAc4aCjRKgEMgdvMNB/WJqh2GiFwXGmvV4Cg==