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
- 2891f6580da95910c831f2bc91f803b3c14d8337ddfd2ee7d4ada47622b4b765
- request
- a242b0d8e0bf87408863f90d71e6e002f96e42a2097ec3454bf2199f31cae355
- transaction
- 1af01d942a64fe297eb7321d473324759f60d58004ea9ae123def5b251ca9746computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36523
the chainentry 36523
- sealed to the entry before
- e5df6cabf42d4fb0ef616c5b62598178858c225d7f414519deb9b9886f567064
- this leaf
- 9f66ba8ec5d92a01f9e9ea8086289287beb62b07ef59f1c9fcfdba29b948a0e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- blOTE7BuQtUZRsFzWiNlaXF3APbwdrZ1yjwvDIWgCMLik4mhmrVoe/xanXqI0IqgtUsO76+4v/7mhQBImA/5BA==