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
- a2590ccbeedcec935d0bfd053e0f14589385a4e8e4ea0f618c19790db05dff9c
- request
- 60290b63c01006627ceb8c6d16c021df94bad49ee3c85661b0ae9f58935902cf
- transaction
- 0e6ff42a604b74a75a10214e4334bf11a6ccb7983e794e8a0002a3d4419897f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20003
the chainentry 20003
- sealed to the entry before
- 199afeaa40071b7f5145d8220839debad2221c6f2245c4f89adbf1da11fbeecb
- this leaf
- 27102b91d8ae0dd8114badc2627b8973e0dd869fa3e2648c19e15504366760f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lxvqW/JLTg5g+b1GSewu+NV+henq3VDgVX5IiHdsVh1z881i2m2j8W+uRI49tV/ghKL5pPl6+MxU6Z4uF/YGCA==