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
- 2a7b95f250855e6b6199c4b72a39df4aaf83d9962e3225fec4e070f0e3f5bd0d
- request
- 218558352362928104f0212a04febdf45be44fa82639c9f8b7a802dba07a5f93
- transaction
- 2bbfba364f580208c40e259ab97cc49d6a5a868c367ded483f95bcb913028051computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75096
the chainentry 75096
- sealed to the entry before
- 0c6f3b616767614c2ca231cf41c3c4249f04b0bcbe1b0606701be1b5215b70c5
- this leaf
- 66057f548591fdf2f109b3b56d9f96facf8036cd792493b2d6a552b817290329
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NsMxz2CkOQJb/nHTBFhMxz5kdsEryk9PXTth/Dpj5q4Nkp0ka+KZYY1CcBxt4enHukv7ks/65PRdL8vmG7EUAg==