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
- 7c98495a0da56782ebefd4d497dd9f94d15041556b284a697967474f9142c678
- request
- 29ab97bd5bbb24c4536f9a508428c22331e188ea29e0e8c04f485fa3e85567c4
- transaction
- e6119544d96e3fb065f5aeb305a676f5509a1aa676881be7668ff2fb5abe0c7acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30263
the chainentry 30263
- sealed to the entry before
- 852a812ec403cec206ba7a8712f55f17a729af6d702b0fcddc385a137f14ea4c
- this leaf
- 265354ad6c2e6e28cd5a5da734671603b595a2d1dbfac6b5368dfcd4222ace36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4VoRMaO0GI6novpW7DF/DbLchak/1ksYE98F6ZXRO7gVHWbLV2uWOcMrl+A+g9bT72fZXjK+8dr9AZzcjK9zBA==