why2 reasons
mandatedestination_not_allowed
op 0 pays GBRL5XJRDW7MAYF5FKRNW5QOP4OGIRSRQYPVQLWGOY3V7TSKDKGE5MKL, which is not in the allowlist
counterpartycounterparty_denied
GBRL5XJRDW7MAYF5FKRNW5QOP4OGIRSRQYPVQLWGOY3V7TSKDKGE5MKL 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
- d1a127248890a3b2957629f47d2d52f4d718492e4f54574947df4324a95ee088
- request
- f0da8e05906e244a8661c20b541ac7fe569c5d142c1c7f67f585db5f9edc3e8f
- transaction
- 154789f80cc3e011a7568c7bae6ebdfe137ac93d87274ad5b2c2a0918479156acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54099
the chainentry 54099
- sealed to the entry before
- fb7e4d17b2aa699b982941d9423e39e3207de665d1f408321f6b978ffd46e828
- this leaf
- 13b00be5424c81c86e8ba5256443e13a331ed42481ebddcfc6eff5226c77eefb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QuPN1FwYh79c0AuIrY4PPreWYwgA0UhRErLvNWbiMpF6WZPNwVkmWmSKJYVWDNu2iPOsXJdKXrxGCgMsC9oKAg==