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
- bedc5c8d39516e462de263ee927472d691baa728ef15cdf871bf51bcfc65b272
- request
- c804dd41a747968a26a34dc8a9fedaedf2c5a41626a1bf0971db7935b097432b
- transaction
- 40f66c3b19db6da0e7caa668f34395fed76fea07495a324ac7f26fefa593b2e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67628
the chainentry 67628
- sealed to the entry before
- c87440913db8d5ee7dc878cef819068feb444dd854b302a96ad7bae23ac8e26a
- this leaf
- 79b7c2afc54591035f0d495f1a84dc1cac16f4d91c7b41365fa4f697ad181ae4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Nt/awQ/p9k1kioSKzb3WVh/jKc/U4qG72vEbXSIJPXXn11FK23JrNLrdqPjFlJhdRexEpr1Fash20DOfH85hBw==