why2 reasons
mandatedestination_not_allowed
op 0 pays GBGGMCSUI4KJH4FFSQJJXEON63BPG23Y5K7V4SC7PK4ZPCHGTEF5OB2S, which is not in the allowlist
counterpartycounterparty_denied
GBGGMCSUI4KJH4FFSQJJXEON63BPG23Y5K7V4SC7PK4ZPCHGTEF5OB2S 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
- 23028eb8b74f143028f1a360ee7d35382d1ec8a9d035d5cf2f3a9ab416fd8f4c
- request
- 72bcd44056188850b54aaf1bc62b2e81a8be49aeebc7da76187b334f05576baf
- transaction
- c463a4d9910004fc5cd19f2a79fbfe42fd5c3d8b068c64bc932541c1dc9b3e9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75259
the chainentry 75259
- sealed to the entry before
- dd5b6f7060bd87424e8a4941f0385a130d4e98e3872a43f65ee751f2aac627b5
- this leaf
- 77d77d9307a18528a00611bbc18ce99e6ec96f572df8067afee899d9b43f1999
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bOAS5pu+iBSA9/PpvUd2zYNi+j5/SITM1KYXNq84OhitUZ332CCcbWXawVSnZkCZqILlIHW7ygiq5IMSKnuBCg==