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
- 0fb9522b05993983858761765c41ef77780e923cc9c706f1ed733a7e696feeb5
- request
- ea195b84abe883181e457a553d1adfd8ff54e174a71bbb2cae32dd992f72fef8
- transaction
- 4266f7d0acd12ab235a09ede5dc94b71307e5aabb6f5fe7e91ce8f2701c96edecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66040
the chainentry 66040
- sealed to the entry before
- 85df3591817fbff5e1759e434ae2d0e633db5a0b215c4b2a53cdac17718e396a
- this leaf
- 6151de697e599a0b4752173f33b73e2f95d1ccc1166a1c4d1f91316b538ccb67
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LKzuMUk2YmUqHD6KBotWCL+Y2DGJhgwcud5lWVdAkH+3x72tHV4wbkKbxqFjmJrFKc3FetiuFIjk1gSQIZZ/Ag==