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
- a54e99e3af58e52fd9b90e7ced6b415345355908b557e0178b3090379892ec69
- request
- bc190ef337f5160df1fe3aabc793ecd64978142cb1251f6c0b231376ab7a0184
- transaction
- 77750c1e3319b4eba61fa64aad5d88b087ef374e1d8fc4ab250570df02f217d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68312
the chainentry 68312
- sealed to the entry before
- db087291b97afd77c6b80ecbfc2d6413013cd06ee753415a3079561564498099
- this leaf
- 7a877aa0527a790af80dd85f8108a503cead3524e5a443c7c8cbb90ca27aee19
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t9De0CdCuuu6r9rqMJP9dwPUjvy+TA2Qk+jsvqNTj9EpymiV03R+aqfuLTHksxLuAcWHQnQSjiyBiK/ZScyyAw==