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
- 7578f586457b28054684e54ac9c9b666b5472b04526dd1d15812df113bedfc38
- request
- 89dda1cf0c04026c2d103b59fce29a4d1e1ea026e110c2762316b3216b37301a
- transaction
- 2dab7de8bd23ee3a70846884410dc6555d6fade04591f4abf9a789e2eb248397computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57168
the chainentry 57168
- sealed to the entry before
- 7fe3ba7d224274c0e16d09493231559539704830e9268f7cc6170c88e59acaf1
- this leaf
- 5e6f034bd41bb28c477266dc74be628fb495aeb9bb254a755463f98d91cce015
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dvzDDexHG/TVVOAi7cM15qXojd8nFcqzqnvzHfmFqqJVPa9GGipk/bLSBLxkcaYhIsOQBSW+WOC9T7IcRidKBg==