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
- f06fe4d359f6c8eb04597bc5a3374f6508ecae91f12b34083a9ee41a4583a313
- request
- 40fcec3e3b541531bacb056103d574bab0d60f9ede1f6b57741376aee958fd53
- transaction
- 98b16cdccf042c704560df689d5f5d50c7d15f083118492e19c1ab2110ef2d52computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22275
the chainentry 22275
- sealed to the entry before
- 058e48e8401f9f025f2a04d95d4f690fd6bf84ac6fe01bf93396a7077e7f57ce
- this leaf
- bb751e99b6382aa53eaa2581c27014b5d5537eeac8619fbed8e17f9716a5427c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HW3R80K0MEX7rMJyms3Sh15tHRiUhclqiuOjquQM83rDz3PcJjc0GReFKZNkvDgXAA6px4hstrz6fmP7T9foBg==