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
- c4e3e06c08a66c04f8319451d47d47a5773c48e50a008c923b0c02df1be7ac41
- request
- 6f9015467b1dabd548e50eb922e5ba34985ab2510052c1567008f95fefe9b405
- transaction
- d052a9fe828cfe57dfe78039277aa586192b67cbeec47322e700461bba5bac07computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62133
the chainentry 62133
- sealed to the entry before
- ba1e5892d9932dc1476ad18c0bd87570547f65dc3867765d247b6e2b6b3ca8a2
- this leaf
- 42582e726b70af9d7f3893f458c183040e7932fcd262ff5aa5ba9623fb978b7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 59ExpngMJ/C3QhkIj8WJRmv++rKkg8oMslwgFn6kWe5Ga7luFAo6h3OCf5Vq3X0d29Dfw7Zaeq+EX0zeYL04Aw==