why2 reasons
mandatedestination_not_allowed
op 0 pays GBGCH46ZGHWNKZT5FFUUZ6DDTLT2GQWG64XHSIXZ2DAKO7J5Q7DSHI3M, which is not in the allowlist
counterpartycounterparty_denied
GBGCH46ZGHWNKZT5FFUUZ6DDTLT2GQWG64XHSIXZ2DAKO7J5Q7DSHI3M 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
- 8731b61b2dad41e98d81b7f0f9f4d98d42683ba0f991f9153d1e3f4abb9264be
- request
- 2b55d1cb760ff762a18121a4fb81d505c0ccfaafe06dece46f0bdcc99d801310
- transaction
- 5420380f9e1baaf5e27775e663c2305978d067d363248c1a190de1970072997ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27294
the chainentry 27294
- sealed to the entry before
- 5f2a690009122f1908008e2211fc21d979b67672769b33af2e89548684d05f2a
- this leaf
- 2c56a55eabb75ed70c44da5741a95e40a36f16e47ebc2ac5a95e86f6a5e737e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r3xhOmc9v6bCAMhTvZA4YO2sAfhNddk9HMQwRIQe1+3Ln6lmoO4+VJx186e35URNMqb3UyMk+Dll46+bQnsJDw==