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
- a397f687bb8580de4d297dd5267ea3d7490ba95a5f15fe15e8a40c21adcfe60f
- request
- a39e295b8fc46c1ed7300da1a99c4f0d876f9df7f8992089dcafada570124672
- transaction
- deb5baf3a5a111b362de0f0929453c333cf640ad1d2684a7f854522be26418d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9654
the chainentry 9654
- sealed to the entry before
- 8c435152d3d855ca03848e0e7eec40a5ca9457e9afbca95285f2e8b0147653f2
- this leaf
- 14a801833e6849ffb60c3755aad18e81a5194d282ca897fd03e124f2f013417e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s+NAjBxnAEsmDoModOvDAZXsQylEDWFaAM9ngDggpYUSO3vw4aGmQ60WE9flkLzJ76p2Xo84nEb3DCpV/pDyAA==