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
- c9e64128a0b08d3abe02a79cfdf28937c99700c40587734a12f41e40a0409251
- request
- 204bdfb70e46151e3c9c613fae3e23406f59d4acc8cdde9c3e1b2bad38be2235
- transaction
- e0ca268e3f17b54ad382e5e9843832444f67bc7092f6caf63b25e1c9b4223073computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74824
the chainentry 74824
- sealed to the entry before
- 29cf2db8f15feff90fb34b54ee3df8a94c838f81e6052f3260813377623a2fc2
- this leaf
- 5431d02b9acfce94d5f3eccc29d23b3604a40bb036ab85726cacc895722fd2e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fUI+GcUahDhayEzkz+cKszGuRoJy/HLQSddgw9vvKxCmtB9fNINcrFJVsJ0F/HXZjWL+mC2aRQkw3SYcFe7GAg==