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
- f40b38a6b1463ecad001b8a00769b388755270eff1b93cc5567359ea93fc8b1f
- request
- dc3f6d84fb76e793dda43d388689bb555a488547034fbe972714d2ac16a594d2
- transaction
- 3101165497b6b2223c2b9e4cd3a9007d5ef8cf1865af1021cfb8b8653d408c26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58122
the chainentry 58122
- sealed to the entry before
- 174213b66804372a932ee9eddffed3bb422fe992edc1562387446dd0f1d608d7
- this leaf
- 5c733f69e53e2ecf3154e1aed985aea00c8c2341f005675cad44973b3ba2a5fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jvIHTB9h/pFZXsVPSrKNFLL26Dg15KmoRXmH2dpsrorAtLfJgJx/SJChp5BgnDs+/BI8bH99MpyrILSH7I48AQ==