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
- bf301a63e1116a47efee5e83e26134900cb8b1f6725f318d9fc53cf2912914d2
- request
- 9ab4d3dadd6c7270e03b31c7271fb3cc0d52040544aba5cda8e188ab8043ef69
- transaction
- c5596709bac919baa19dc250c016a9c5a32cd8533ed5e2224c2fb56902f48449computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27509
the chainentry 27509
- sealed to the entry before
- 545e0b1f53aea7768794e15b4a064261f487e6376a7ad4b3d7e64b352fdd5c90
- this leaf
- a35f42c6d4fc815b4bead96fa6cfdfb5154b950b2d11f6ae66d45b0bd24b87ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +kJ4xjVzjD2n/ED87B3RFubujSjYW7NAYe0+K1NHz6frWIRkAEZTEU70qiiPbu9B4SSOtQAxly3YYzRnbU3FCg==