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
- 535a3192861302b1bdbf0a153adb85947e442f9be04fee2c64d83c3f908aaaf5
- request
- 763ea27f32cc276a4bf485445bfdb4059f4d0984d72b3277d1e023a5ebaec8d4
- transaction
- d11fc7bc126fba51d208ba8bf1e12817272e9a92f33f646f3a1edf73699e9a82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45028
the chainentry 45028
- sealed to the entry before
- 379ef6d59a9502a73fe8a8e1bfae30365a6507fb5d43de233a3f1caa59227d72
- this leaf
- d53583cf13f10db9b45e542f375b1745ac9fa10b6d82f8a5eec3df02c80193b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Jo0YP55itNoa9njL428q8JAKJ99dF2u7VdVKLuoWjYLO9PntUmAirjSNO3uPGpHRoV4MC8ptbkPeQDkORXEBw==