why2 reasons
mandatedestination_not_allowed
op 0 pays GB4EEWE6NVZ4BA53NL3AN37U5ADPHBILIG7JEEQF643UTD4JPVLMV2C5, which is not in the allowlist
counterpartycounterparty_denied
GB4EEWE6NVZ4BA53NL3AN37U5ADPHBILIG7JEEQF643UTD4JPVLMV2C5 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
- 2df524f5dd08ff3ffc0188dc6a4ce9a49baf907b2b0fc3f70e7599fed6efd5d6
- request
- d5f238be5316e6edef5d89b7a4bfa8e57cc06b97686e8373aa6f6d60d817ac1f
- transaction
- f4c74c9161cc45c8160e7669b1900c234fb3cf05c81de16364418a468744ce2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48615
the chainentry 48615
- sealed to the entry before
- f508e53c335646a7bfc103b7a3e40a68be11cb36b8f24c239549bf82ed4d9da7
- this leaf
- 1232f1c8db8551e56beffa59d014cac40558b3c0ec972dfae0af4bce4ca7d348
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V2I6YIQXd/bIYiGPWy5FMULsf7CNsUIZ5KeKjv//+go1MaIRBQAJqCfLf7ibkL3tRbrkFPW3YOl0qkvu++mNBA==