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
- f2e12880e06aa34a24df1f226e4e1381f7ebe5fa938c328b1dc1929f3d9bf04b
- request
- 30aa36b135029469bfd3d2b2510657cda057e0e5bb2e69f97dc99f426e1ebb16
- transaction
- 539dd5e302ab506bddb10e6feb8890f68717fa9a215ab455030622df61ecf586computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46362
the chainentry 46362
- sealed to the entry before
- 8b745dbb92bc2a1c5bf3132c1e64aa2ac95d9ff310cbbc2c62355368035a269c
- this leaf
- 599f0abb95cb6155940d3bc22869cc0c01d6b915d80d649f3cd6ade1b52b0bb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Qz4Y4kc6rbUb0S+kP0iRByN7xn2me3AMa8OatZyVRZWCmOr1ymutExymQHD5lrB9SWUQcD2r1rIUqw8rJoP2Aw==