why2 reasons
mandatedestination_not_allowed
op 0 pays GD7A5JANC5ZLYUWGDKCEAJ4OUQQ6CRTNSPGWY3GLGTTAEOH626U2APWH, which is not in the allowlist
counterpartycounterparty_denied
GD7A5JANC5ZLYUWGDKCEAJ4OUQQ6CRTNSPGWY3GLGTTAEOH626U2APWH 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
- 7cd0befb04feea89d1f7d1411bd76f0d877bbe44c915d2e46970d83ed684246f
- request
- 3428f0245c94bc78871986ccde101203d3e62767a34224f17475581943f6d05e
- transaction
- f89d3c1b7100ecc77dc3483da5b865d2a9ef78f339ea6632ef8eca4727470c57computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48469
the chainentry 48469
- sealed to the entry before
- 63b8b9478fb5d2007b5de45db3b332065d35d008543ef0564ab3e26468d09987
- this leaf
- 738c2bb9b9108f5575c8c80c88e615e0dbbba3717e69f4c27dc250d71070dffb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- apDpJz05x6CjH7HNrrL8hOHCp2+MWOOmRw8p3MAk1pUNJ78F+11xx7n5hYI198IQfcGuhgQmNfK63MuDk0OcDA==