why2 reasons
mandatedestination_not_allowed
op 0 pays GD4RNZREEN7JDY2RK6SZSN7NPO7MK3FJCB36EYVNZYPV6N3A5R66JF35, which is not in the allowlist
counterpartycounterparty_denied
GD4RNZREEN7JDY2RK6SZSN7NPO7MK3FJCB36EYVNZYPV6N3A5R66JF35 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
- 4f5c592eebd04efd2ef238db7b1f8c354164d6607e86a63e259b196bbdceaab0
- request
- 545a826545a29b96279829512af6c447848b98d6838e3e70919d86560e760fa8
- transaction
- 5102644d8b65c07082f2bf54b104491d33527f8385ebaea8aefe85262a65a4b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 102
the chainentry 102
- sealed to the entry before
- 79b95460466c0c4924d1e0dd19318dff96626325c207122e2ce3d35736faded8
- this leaf
- 01dc8b90514d322c069d6856f290ec8ef4e0b6fee0212118e846255501546f20
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q21xWcVEnHGuw0RwA6o8GA2C/kYqbu9gcj6xKTBu/I/FI+K5Ku/vzw8Ifgfef3L0gsr4/l7JeL+4wWWtimZ8CA==