why2 reasons
mandatedestination_not_allowed
op 0 pays GBKSEAEDY5Q2G6RTI3KFNKRUPJJTAWC5HMTMJJSK45Y7GIXE3BOOSVS7, which is not in the allowlist
counterpartycounterparty_denied
GBKSEAEDY5Q2G6RTI3KFNKRUPJJTAWC5HMTMJJSK45Y7GIXE3BOOSVS7 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
- 19b85bf9e19ffafe2fadb45981b434316a6c0ed7fbf74fc9eef414ff56bda3f3
- request
- 9b672b39cd2ad4c929aebccdd8bb7a32a6f5f68ca3719a651b54ad0ace14868d
- transaction
- 8def2836e9c6ac822265deae0ea2e7531a18a69b3bceed781dc4807687dc0ef2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26132
the chainentry 26132
- sealed to the entry before
- 5bfa91e3f9dd3af347cf5534ede83120073cb9158fb5151b11c7390082c19cb9
- this leaf
- 665d7f018d7c84b375383528180acad1ded03bd3234c1dfc22b003f25a92ca63
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2GPgHdaFHemuj9p0TUE2gCur1eY14bpSYMGjVePrasd8ovLPcqOM9l713X8ophXA2lUR9J6uLMP770dOjI/GDg==