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
- 18309517ed747a229003c6703ec2d4092b7bd2adfa0ac41e710f94dca813f0fd
- request
- f2ca8e8c7fc9f3ff7639f13eb9549c8453e830c42e3795b57a957cf060d22e11
- transaction
- 87f8ad723d82c932cbfe098b09de164cac5ae9ad8cd19707eb1f6c12c1dedd4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50092
the chainentry 50092
- sealed to the entry before
- 22d5c9e627ef7a95e66cc8759110600b83119b6a2192f62f73f029e1ee172f0b
- this leaf
- cca672f6f251121e8ab8320149a3c28d6abe81ea7dcd0055942bc82f73dad5b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WR3tfUfeIglFPdC0FEoQ51nwaOl9LMf0L1TsX/l2fNLOh34qq6qjmYC/Mfte9/lHAY/zFNu66vKavSDwZhmZDA==