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
- ef57853f9c9d01896481efd1ac2810bf9349c188f2073b00320e73c6374154d6
- request
- 3164023d3d198d633f9efeb026b9d842a6d9ec62a930ffeca23c7bbc75e84697
- transaction
- 923c1f2294c49ed31ff9fdbd94fe884bf3dd1709b710facda88285162696442ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32875
the chainentry 32875
- sealed to the entry before
- ea781b7eb2a890e852c2a1df99f819a54737dcede8d8612221f1c0dcf2c6cfc9
- this leaf
- fc8d38ceece91ffaf036914f22bae139e45998b5e0884f82b97b4e813fd85b25
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hne0OXc0tK29DhgouzR8x0git+SVD63M22Croj8BZqF53BEf3/49rPDvhYt74G+rrI5+tx+Of3c34XCucLLzCA==