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
- 0bfa8dcbe6da4bffc48d5a098801facc24b2add3fc3c3c17106c1172d57d499a
- request
- 9723107fdf26c19e14238ded6a7948dd644eae99b6b0f9cf9ed44aa70bed8947
- transaction
- af03592fe4d6120429e30e4b428030b57056ef1608329f0ca4fb8f426241b737computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15667
the chainentry 15667
- sealed to the entry before
- 33a408b6854b182a53324a0468e4b7e9babafe44a1e654e68a9e105f87960d6a
- this leaf
- 16682ad3a7645ea0ac5ad80a4504567516b919a478c3e33ee561ce6dfbd1c645
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q/oJeM4iUlg45Vs/aSBYh8DxoOPaOPyM6iDTIylLTGKJO0AukpRMeg3y2M340UjXYdr6+lHX0pq8KB+I32vxDw==