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
- 958f102fc21c02dcf1f8e62ac66d2939c71dcb98380d7336de22ccce6f378550
- request
- c8479d2eea3c039e1dbbfe40f1403a09379cdac4b0bd3d994b7b44f1ce349c42
- transaction
- 6357e2f828acad81c67ae8316e32ef44145b233efdb37b7276c4e689da12620dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60039
the chainentry 60039
- sealed to the entry before
- 9362570fd25ff8574743a10713fe808b0b5ef750efdf1d80883e1c1c92963724
- this leaf
- 36fa7c4c32d678bcf8e38abe2ce469103ce079271a0cea4305b9fa4545191c0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DhWN4Fu8RSVzBcsAs9+luNk3aZPWU7JnYhmRev3w/HSWMCra4arUWoqheQxAgg73XNhEUJEZcGiZC8fgb9n4Bw==