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
- cb0bde24f785cc60b18c1e6813b2651d2badc0a1f60af2addb6d29532b3ee255
- request
- 7ec1f202f42a6d0b5daecdc941071fd29a86814de5e8b3d9bb90ca57a3588305
- transaction
- 73b49f369fb49a9a9701d60c3a3cdf49e2dced568e1e1952cb7dcd4b00565aaccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25667
the chainentry 25667
- sealed to the entry before
- f86e50986e5b419c24d9072535232dc69de6520c1cfe385dbe1e2a63523d4f83
- this leaf
- 52989a263fa90713c70b2f14f3e63739d7d7898370e1a8a606a4c1b6f4de4234
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zbrbMGiZZ/dh84KjZJrKpvRKYc77naV+Qj5i/RQeBOI4I5GpqoruErbp7OIuahqo2RdVfAllEkjDHZ3Lp0gmBA==