why2 reasons
mandatedestination_not_allowed
op 0 pays GDINWXKNHYHGIC4VPPNRJFTRMWCPF4IWWSQNBSCTTIM7RMTMEM64W4QA, which is not in the allowlist
counterpartycounterparty_denied
GDINWXKNHYHGIC4VPPNRJFTRMWCPF4IWWSQNBSCTTIM7RMTMEM64W4QA 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
- 4365f879f8d8a9a458b548396bad9101dd52e7271625b874d36293f583bb7ef0
- request
- a1b2a94beedea6683b4d9b3f8a14603e92a22fc8aa9494ae5768f159dc4a73b1
- transaction
- e0c35a50235ef22c95dd1b0e74af8ac04bf280275ecdf13c45e6b27791e1d511computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77043
the chainentry 77043
- sealed to the entry before
- 158a4403bdc10ac87bf466c3a4638566c15ba7e619d974a720774a33d0e5ae77
- this leaf
- 2bdc2d03830131d16ebefea1fd5bb6680a16d168b253f60ca20842885c999333
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R3wy351tMrsx/IOjSw2fexG+fQFNA3bpKtlXKtb9DJ/fSb+mHM+O3hqnkms2OgBYUdTHSZ8fjXbzGY4q/Z9GCg==