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
- 91a33e023bbcbbc6534c8f9ba9f4053fc0cc4686bca177f450347da4a76fd3e5
- request
- 43fb34801fb455e6ab63e7a5349e41993c4c10ba6cde3730ac990b985b4b8f19
- transaction
- 8be355da262676c74e86ece1ad3439a6d1da736b0714d808d89ff9b554d3ad57computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34525
the chainentry 34525
- sealed to the entry before
- e4b49273cb71810bef431aac563961b96bba07e0559537a3a37721610cbbd8b6
- this leaf
- 9d286afe8dfcb41af8a01696ba2191030026830b31f223d94c3aab99d6a9ee4d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mj8suVf1chVcUHMrrLju8J+2yRrYYKGRMOINcDlDORFO62koaB0B1EjwafrjlRtPaOm5h2lykGx03zkpXFTBCw==