why2 reasons
mandatedestination_not_allowed
op 0 pays GDFQPYQBU3TUK3IV3SISL6IXHJJLNIPJJDIJ6URIZZMVCY5XXISZ2QMO, which is not in the allowlist
counterpartycounterparty_denied
GDFQPYQBU3TUK3IV3SISL6IXHJJLNIPJJDIJ6URIZZMVCY5XXISZ2QMO 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
- 29f1fe0e8328d33adf7b7ccaa003906c22c4cdcc5c99fa666ab275b34cd239bf
- request
- bac19e5090c3c389f3259e29029460f11bd034be129b1832f6e22ce1071e6e54
- transaction
- 43b034851cc3102028877f0778930ecb6a78bf8fbe14a6f0d8eb690dc3250dddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65050
the chainentry 65050
- sealed to the entry before
- 02ca4003ea4cb38a95ca367b35b92f424642356f721abc487973a3c5eb6fece1
- this leaf
- 1c7827494f5eda2fc2c40ee6331d54a4751589ec74658be9fa4b00d29dc56485
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KfYvbEk3BnZsA/H5ihYmzhZ0vgxhtqujf98obz6zIdO8bbodMT0SG/sePV2cKhxnBPhMbACdu99J0dKijVSdBg==