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
- b28cda80172d04c488a1d208c55a915f7b9669a1ba72959b9bc2583f2dfd8129
- request
- 700c89fcded1c9308f341c5171682dd446c37da4fa1c50ac1db84427ca663df8
- transaction
- ce329fec3315593eb128956a7147fce0d4273070500a3e3c98392215928f9de0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75269
the chainentry 75269
- sealed to the entry before
- d10bbd1acbd64d33cbf37c4d1ab97365cc7514d6497158acf67fe06fd9262309
- this leaf
- 71f8b013e2151fd2eea0ef0a267cbb334c68175f67a5acbbf979c75b49829bb7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a+JSOHYR4/D9eM64VUhdKnbGZ8Pzmf8HxyktAwjXXl9CaMoshLUogvj8KfdjpaH/VDigty/BTeHk/F0f0IXICQ==