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
- 3c101308d035c61b4e88a47a85d05dd8afdd132fa2caafe0f991e50e3d394b90
- request
- 785529ec6d334313c40975fa37be102bb62d9ad7d2cb4fa7cd51560de9741684
- transaction
- cb9ec4e928837d619d0e1ca81959236038fe71615ba0c68eaed5a1343bf3d4c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73925
the chainentry 73925
- sealed to the entry before
- 59abd0a0f17b961b5166884bdabb4a33ea771476463cbff381e6899c0bb4fd09
- this leaf
- 90b06837a83a60b2a2d67f3d9aface19ce44c2f9f6398a5899a8a776b891b539
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xPa9wc1Ro1fXUT7stf4/CoZgerd5zDhIxpOZnjaDT78oogABN3CoTBHKrgAgEWUEVbmf+1dyCDeNkJ74aSCyAA==