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
- b3c3ae81978bcb21bcdb9f46c04486f543a649ec5bec8f9f5376c8ad698bdb47
- request
- 3f44101b6c8c4ffccdd95a94ddd10be62d3081f163bfc2ce985936343bc823e4
- transaction
- 1f360c565261b137beeb6f172ee1a299a51bfa1fcaa5b3ea7429c42c4d0cca86computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54179
the chainentry 54179
- sealed to the entry before
- 695b02ba13ee8a068dadf48d75be3ae6868359fe0c7ec5b6d4962022a799e91c
- this leaf
- db4b6cb7e0f02c2af86f5ff9096057712f4dee3e99db2efdf782d4a0fd715f36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OxB7V0DxaO+BiYABjYi2utnNysKn54wzXxmhurS8mDj1r1vi1WY86IhM8scst3gUXo4M49UIwzzLOEDgVyBEBw==