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
- ba010d1f9902a90fb502d4c449a008f8bedac529e5b93da47af67a0bb2b99e0f
- request
- ebe5ea8f026eca795ca9b3683ae120eb696231e4ad9aa7f5f39e4d529b5cfa72
- transaction
- 5eb07b97715048a39a4ba8e315e9689e5951908f26c15df3650537172cf050cccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50077
the chainentry 50077
- sealed to the entry before
- 980b0c4a8bfabade3a2da67235288f777045e0276b247f22bf9afa89ffc0ea30
- this leaf
- 2968fb01168ef1c784a38bcf8fdd83c3825f924ca14c49e08f09e98021590015
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ci42uogpslc3iX70WQl/TTXKzruH/SdLFgktyPfH0pZl66ZosyUgsBcPo8+aYh62kcixQhNiDy/LMen0AaqsBw==