why2 reasons
mandatedestination_not_allowed
op 0 pays GBN6J5S2SAYMLUYYSTVS7DH3J5A5K6MRPQLVOMZRY2S7NSQSNPPI4EQA, which is not in the allowlist
counterpartycounterparty_denied
GBN6J5S2SAYMLUYYSTVS7DH3J5A5K6MRPQLVOMZRY2S7NSQSNPPI4EQA 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
- 7855453566c8a9af3b364dda634bec23b87c77c800c62945cdbcf773fed11807
- request
- 9665138874fc0fe7739c9223193abab04d2623b92fb63a68080a6309e622cbf7
- transaction
- 69e1bc7a5953d3037aefe0aaff46036d06a82a0dc27ab983025d74eaf93db2a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35514
the chainentry 35514
- sealed to the entry before
- 054cd7ed677ca2b0f7bcec6732ff709f6c3e7ef1c87ed0dec939c26ee53b4027
- this leaf
- 4f1492bbd725a24196d19ec860a224ff50d2412d36e871e7b3eadbee0bbcabd0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OMK8OlPHzK3A5IFfn9W/QOlDR55/jlex5d6X9lMpUa9RC33iRJCIFN6V6C3Dls7Ry2BcMipQl0uSuFelAQNOAw==