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
- fcaa828d85015bba0e4247730573459f7105536bb4a2ef8783a69fe7a08e900c
- request
- 6b2cce3499d518133f2bb9e2296605b7a6342bac8b2a8e9fbf47efb0d431d98d
- transaction
- 8db6feb461cde4cb84bc9e55bab26fd329ae01e6807ac52a3012a903607b9415computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22660
the chainentry 22660
- sealed to the entry before
- 86f42942b7e2dc4dd7c903ae47f1e3077ad0abf47c19ee269268a2cdacf3e325
- this leaf
- 17e76e6274fb29a6e3330802cd4b88ba3f5425d5e2273bf0ede1cac9f7d1161c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MVZ3NJ+7UY/6/GLJ1UhQd/Thy9m2ZnxC3r4OCsoLTNDF02HZO/RaaQyaCTbPTo0AUeKqy2ah+f66Vllpv78rCw==