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
- 96c46b725dcc40ec5ec9ae2ab523222ac65902b1ff7bcdb323e356ebeb58a7f7
- request
- 33779e69199f857bd42625c081ce441df264558687009807314489f5a3b0ca44
- transaction
- 2cf71359926c121ece3c2b2df87640061530cc8c8fdcc1a900549c234af7653ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22311
the chainentry 22311
- sealed to the entry before
- b5a29819b8047767563d7b6f01610335c84870af9b1045f98af1e88d17f44ae5
- this leaf
- df6c845559064a4dfbd2793b50f3b002b6848de3c874d2ce1f2c77bc5f9c4208
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bSAW5n7rRrzxrQaH+l8lAGi0psGiEEaodGG2dOfvCpg3bCQlHR0I8+K0tcITpCJt+GjkX7Q+y8x+3YAjDH+mAQ==