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
- f559c4934e936d4608cf41c38144cf0b299120c85a98428b3a30424805cebe9d
- request
- 1f10c57d3aabe69462ff5e617d2ffbaf19560f009bd1e6680af8992b9e60f6e2
- transaction
- 351e06cfb80eabfd88e19c9712b1087f81a49d141c467450990c2f04f58cf4a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1840
the chainentry 1840
- sealed to the entry before
- 33d6dedb0ff00560115de444ab85acca8418997ee6b37e3e95f125e368c5c2aa
- this leaf
- 66b74e90b158c5e7d1c3ffba7aeb3c71f262bdf953510ef30ab37d4430ae96d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xej89ACQxweV9R9H6K6jYElBxM5mISlZSt70hUfAeYisEsZARDaY+oaJJDSG33CKir3f42G+bV/GVdD4zNiGCg==