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
- a97d0713a15cbdbf80b66d0eec6fff06800b935470bc847785c5e8c95cf92328
- request
- 174016a9dd91922ab5f779f10386fa4f2d74bcd916f4e7dde0121579e4c09c6c
- transaction
- 25af2f72b12c1025f6f1110777fa26a86fad21f136d2fffb507900c92b576aa1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30615
the chainentry 30615
- sealed to the entry before
- 960e78058f884be8232980b94820c7d7d5dad8988d9b90d521456f5df69584aa
- this leaf
- 9348f52dfdb8eb2d382711c264c640488bce31377487d673e14072a219f3bae4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7sycygNltuJnb3nAJzI9Tp/GLBpgxQOQw5JR67lZBrcwW9VcSiDl0Zmrm6+JGW8ABrQvlVBX0BhhkwVOSLj2Dw==