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
- f22b575f5afef99d926b1f3198308664e887f7078d1f2c50d8a2fc40db3b11bd
- request
- 12ee50d337e9fc1ab05a2c2d553748967e2ec8452579b4c233b90abd8011be16
- transaction
- eba5f4e694a7a5ec41260534c21cdaf2cf2efe7c0c794a0dc0cdc9058916076acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35668
the chainentry 35668
- sealed to the entry before
- fc0869b780bd31d611797335f9d693e0f476b1041a006e25f08d533be63a461b
- this leaf
- c25f7570bf25924fc36d733dc8df2deb5b077b289e423ee96192152fd4ae8f92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vleOxS1qnBbxXz3D3SFmIHizc1HIKEd3SxcfuJliHJdykKLXMpLiPrKaXRl4My96x41QPEqX47gKeMA7ZPnZDQ==