why2 reasons
mandatedestination_not_allowed
op 0 pays GDMUUPSLW74EAVY2WO4LYVB7UVCQERIZWLFGOIIKRHU7C4JDMI6LQWIS, which is not in the allowlist
counterpartycounterparty_denied
GDMUUPSLW74EAVY2WO4LYVB7UVCQERIZWLFGOIIKRHU7C4JDMI6LQWIS 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
- 9a9ccf7a5d99c8e8221ea462a527abcc40fdce235bc4242c57f28010f241fa56
- request
- d683ba90541596e0af77667dbda9a9e95a487e6b74824a286fb48d5b6afd64b6
- transaction
- 9851b77bd4644a671d813ce732390364b055a3995fdc2d868d00da82d25ddff1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36953
the chainentry 36953
- sealed to the entry before
- dc099e08c39b38315a2854589be840e0856077bd686ca9eb888a0117a55e3247
- this leaf
- cfea7864fe269cd612e911093891ced3aaad9f4cad3afe0f8c43d8ca448471c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TiYu9omX+df/wx7dCYXC6hLj2lmBRLu0dA8SagbzkR+SzA7fJOiFI5o+aLLUjUEahUcTBb+zZI9KKEIk9hc+BA==