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
- 9c939bb75c59c99bf23a5e83d7e375549c823c4789dbb6113c0428c171e4351f
- request
- 2772715d678b7fda6b2542b73d24d48d9cac94196985aaff372ba0f9f04deb11
- transaction
- dd524149b0bbff6c6697ec6de4896fa661141c05f18a8c19ba2b0b8f573594a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17625
the chainentry 17625
- sealed to the entry before
- 7d1a82b3cc9f5fef8c668533d461916eb14228524c7dfbdea8300693097e1f3e
- this leaf
- c3b7c904a88e2dda9babdd1ce2834c046ff2d69fbcab393caea65bdacee0af4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EO6YJyLDR3Pz6BeZLpJfn83N2AvUJI5PNBAAZV14F6lMTNCvGoB33SXSBolkYyMIm1pNJAj28D4eFAJsshBKDw==