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
- aa73dc8c5dc6dcf4f04e4cf0d29161bbeb39fe0e3afd891b9ac3ef6b99411517
- request
- 0f0c32eec0355074e88498fc6aa10d8c901e82239b6eb2d3b527b4966cdac407
- transaction
- b3f389a3c57693798ca43f81f9d9adc5d211ff88abe133c5ef699999cb706016computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48391
the chainentry 48391
- sealed to the entry before
- a246d3c861f96e91c38d26e9af604584c5eaf851c7ed4448f5450a3d72fb3431
- this leaf
- d679aaf68d8a6cb8d50e9bfd00bb9cbbf6556b18c87f9a2ad5cc2dc922f7caab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3gZ7fdbowzmDGMmR/FzAaBwjfBFNGiu6Qjmda1lDOmNqHctAnhVte3BhjjR50S1QEW0LQcGo6aj4Zt2EhSQ6DQ==