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
- e9453924c6acacbbe319a81e58d18b811b6232a89fc37ee7b1d9dc5fa4f65e3e
- request
- e16b948efaaf535150ebcc2b917168093685eeae2c7c5bc15eeb97c84f76e8e9
- transaction
- 16fc53785344484bc2610875f064d1a29fd0f812e67ad1cf985e81f81cae3fc4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34777
the chainentry 34777
- sealed to the entry before
- a3168c8d91449f1d3cf40aac1a84389f1cffbd92a1505ca428114c1c263137e8
- this leaf
- cd0d36a133c4ccb728f06723d86603dc53c8716ecaaa1de85b6e07aa4cdc01cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- j+uzjyxD93Nk9anpnquD34Zawz5wlQQuQLQYQgCERj8LgpKlZFeHASfB44fNXJKHpg5P07kZSvB1W4KBaBNdAg==