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
- e57769e3910ec7bcbfbb946dfc2d3d6db69ea75394a1525c2302d721030619a3
- request
- 7d6e2be9568151ead66f7bf3fdfc0d28c988754478181b3df629bbcd1d89c6eb
- transaction
- f2af3ab0d0c2e46d72b83a5cd1c3473ee629bced0f55466abc728dd083557edccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12534
the chainentry 12534
- sealed to the entry before
- 4ea56d5d8304dda9b48cb8a14d34f2c53b21ca55c92d63af3f6c1cab69df27d5
- this leaf
- 87f30274e96a1d307c38c068d44c94ece7b89986928cc6a913b4cff678e6d732
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3tEK841824PwbCWbdKBuVnCzMZmxAKtwd0aUDS7u8q7XNnkV46ROJOe+uHjEwyTZ9aHgzEPd8/24jdkkt/uKDw==