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
- 2cb8872f14e1354b6659553d343663f627047ed56d260aac3af001149f56b39e
- request
- 3733fbf64a563936f46f6bf4d74175b51875ccfcb76f05fad9bb9a3f0b7557f9
- transaction
- ff0d83c55b1f612b92e32ed0dbf162450e35e32c6156574060286e1c8ab818decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75545
the chainentry 75545
- sealed to the entry before
- 7042a9d0081670213b8faa5e0c2a2bf14f3f1ed3b162d0951bb8a1e0f47973b8
- this leaf
- fc13246d1615eb497cef7f02f7a5454064960602f7607c5a4d85a4a9e6b47a12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tet7Cgk2djYNFrGGfgBnPyoxzv+6xv6vFJmBrquzMxuN+BDfSn6T8y3G2w6L7Vr/vmtLy61aaJoMHHjcBp+MCQ==