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
- 60764b57940fde83ea5c828c0f3ab83ad55aefd90a113cff3a522983451dd946
- request
- fd00f1f3fa819bdcacb7cc87ac9c0613faf52605dc9f4abf0dede2ddaf0d9ad7
- transaction
- 9bfe072a5f27bf84ca8b9a115fb524660e5b8cb588663e442fbc7395cc12447dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49975
the chainentry 49975
- sealed to the entry before
- 72684149df5e2191786232e200f2fa3a869f9f53c761e7a3d4e0d3d8f4db266e
- this leaf
- e7c8e207017fc41f19002f1120f1d8a98db767987962f02e9c1681c70d8403cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LRcrE8X523r0SY11vZobjjEahKYlqsLmPheyVMRloUv22DlME71t2sNCY1WAsRkO5M/dYog7GepsU+w5iohPCQ==