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
- 8cabcd56fbd302b93e355450a79f825d83b611d1cea7384709c1a5fbd87814f3
- request
- 6aebb39d681720d138ee18b78b7827dd17cba7fab00bebc81a064510534c4087
- transaction
- 02bf58fdef62d092156dbadaa4b67c2b3c6e669ad80c79cfdf0f5529f73c1ac5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75586
the chainentry 75586
- sealed to the entry before
- 4744d68deb9309e447e71cd7b88457646af5730bb6d5b93691be40e583343db0
- this leaf
- a493ccb587e74e0b99ece572355d06544fb6656014c64037290ba0a44848ed58
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8ZrkudCRWhr8WefAqc/iE/v0aXpjWxGmu4yF0QJ6c5/arOZUVDNEgfpHFC2lovO0o7Xs5ahe7NBTAgYqeKtTDg==