why2 reasons
mandatedestination_not_allowed
op 0 pays GBPPONZRHCNUX2OQI73FEJURVQI4D4DNCKZFYKLOJWK2DF4HBDU6MM4I, which is not in the allowlist
counterpartycounterparty_denied
GBPPONZRHCNUX2OQI73FEJURVQI4D4DNCKZFYKLOJWK2DF4HBDU6MM4I 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
- 3742b716045d5825d2a0e0028ec0795093b15f4f0bc8009452aea97cedc3f7ad
- request
- 0d7ae35b6f9ab9c07b4e352ddfceb401705544cce3ae93fe3be8d1e7a70d1ccb
- transaction
- ae9e6b7baed5416a776f2564935a3d0987a9275ff6740bef8176ed00e190273ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2551
the chainentry 2551
- sealed to the entry before
- 06f53d84879fe4d95f345c88cc87370421944ba3062318eda34543af165017d7
- this leaf
- c60e29b02de73d576f302c0dbf33fac067830d5c900c619fe6ab122eb7232907
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0+krAXuwANu8ugSztQagp2Q8gMcY6QWh2ndkE/Mf6iGUW1iG1aUUimZvBA8sb7CVCME9dU7Y0Ud6lG8ha02rCg==