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
- b8047f32a04cb44c0ad1c88db34ac3f8eefe7e119a5263d2f36a5dd9cb4ad647
- request
- de2d8daf76d17ce0f3f70e1ff25fb3c623c75475f803a586e77ca88868c42102
- transaction
- 11ce884fff511da1ad6561424461e64d28990a086a325f2f42dc9f1707568a3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36377
the chainentry 36377
- sealed to the entry before
- 8993a9eceb9d868df2902f4482469c931adbf73b8073c65504378e09738f55ec
- this leaf
- 82b67eab183775caf96087847d046d39e18418c2c3493bb730c5f94b1ad1c2db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 70qCxaIUNA07bHIhMkq+JArztuI/YvUvu7vBNGArKNmrByabaEVGP00+BAzj6ezSwARuVgH7S6+lroIPmegsAw==