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
- fdaf5bcf54e6eb347a152ec6803fb93771ab8e28c16da40e63d035ef18a79462
- request
- e7a09c71adb105aa7032f14f0ead4a0d965f9e1f74dca1f7921d5ae8111b1e29
- transaction
- 888ae6911067326e710b3a2b26c57a9b80fd47598b1f2e2291d4665aa07778c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62302
the chainentry 62302
- sealed to the entry before
- 9f72f1f29215b5d0425b389a045e24b03e711ab307ae687daff2c763e55f0637
- this leaf
- f5ec1fbf23952f7ded419ad082860ff97afd9672506e03e27397638912fee7ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ICoBS22QIl0MQ0zEf613c84F0J2o5MC0MNU5NGn/eBrT8jgA2jJz4cCVrkf7c8o0Pwse5BLFJupwhNaRgaGGBQ==