why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 47e128a9a95d32782c30bc385f4304cade9894fdf5336c3d2c4dcd3a6fb1f6c6
- request
- 40077db42292ffb4233462db64220d23f8d2dcfa23436e92806df6bc50c0779e
- transaction
- 42afd56ad9a462bbec09a90ed12609bd524897dc477b15d41068c2d53a68a4bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6643
the chainentry 6643
- sealed to the entry before
- cd39f1a168af52035d218b06ac985a19973afe97b59fbf0a56fd577e3e668ce8
- this leaf
- 91086f4128264773f1b52b32ce6e7e6acd47cff5101e1addd0d8a49c5f904600
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hHEPm1FSVzJo9YpewKHP1C42kBBqZqgoWQwZGTMbsPKCys0JrhH/Dhbc+wpSESy2qQd7thbo/zbPTSUIrrzhBg==