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
- 985868b4e4e77c9b312a4a188f7eb6d490845a0ab574f0ac7f5378f51125d9c2
- request
- 9d26ebd61c480051ac21fa4c966cbc8114114c691a76a7a686d1499bf2f63680
- transaction
- d6b0d116648e7830f5da4da4abc78df68ab67f3085eb1e44a59e10b3f90217d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56920
the chainentry 56920
- sealed to the entry before
- 5487dcef6ec96af4695dc788152057716d9691326e1112c8dd1140d19133c596
- this leaf
- 8c521558dc8f7195e062953827c8e8806f0bdd0d3c46d5e9ffafd163a9446cff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WIjMeI2vqjzFe+XDSdd5Rc2oIpmNWdZ+6skT25RI4IdsaeRaKMO31O82gj1QoTEvsAe7taFXwYepoJLBqpdGCA==