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
- 02518261c0c59e06d90e69bfa93f91663e27b0197a012434ffd25f960054508e
- request
- ca03f5209a7ae6748e132b47bdaf12a04622c56ead70d73a7b0cd444f9b4d510
- transaction
- 9d80f48476b06b824ff527c91f6a10897caaa8cd116026ffa1323352165310b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48253
the chainentry 48253
- sealed to the entry before
- 511985a9ec1f9f7fbf71ba7432408562af054eea84f8b1739ba4e137c0338152
- this leaf
- e0e15f2a0d4ea1c2956209ac0e9468e12f83e9f1ecfc85cf9d9452cb818616c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xdNYPcYVCshRRNuQZw3NK4nu3KW7jrYeOCtCe817ac+2lQepI2wo21zmtkA//r2sZGO9eeospyYNM1VvMosyAg==