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
- 366470213fd424111048304f239c6dcde3be4fc99eed5d0c8b161d4ac5e7b33a
- request
- 48d22f18082e153484e65c0971fc87f5cdfc1968b6bcbd4efcc3c915f7b4ebb7
- transaction
- 0c87ce783e011fc77b66409c656b83c200af6fe9377ac50599efab1d21916806computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33491
the chainentry 33491
- sealed to the entry before
- d5b78e476fd7f3973d0a2def710c6f1c13c68a57b71c5546da58485e353951c6
- this leaf
- 010b415de697198c02a92d10b839d705545622cea47ec6265fe15089b01bd682
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oUf5FMH3Ui0rcK6S7A8qIQxYV2ZGNtaNbJ/xy78p2aEovFlRTMDpi1RUpoJu4SoKn1WJG6dw6nASMGOzYcSFBw==