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
- 3c3f4bf59f88974d245778e833548ee476c8f63f05c15d85afc993315f85cb46
- request
- d4b2b99052c55432217b3af5f46d70ec3fbd85cde1453490d4367626b1b8097a
- transaction
- c646b69cf8de0bdaa84415389923304cdbe85cef7d908f922543576495ce4fa2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64321
the chainentry 64321
- sealed to the entry before
- dde3ff1f797b2d1ddbb58c78f8e90264c51d28c918e46b79092cb01303bd721d
- this leaf
- 543605388895b6b8d365c44932d30bf67d09c4c5d225ffb26f3dfb5fb3e37c31
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2KKHNCb+ZROpEfGkLQqQ/mPPGowsXP39chQSNoeA4/AnZ4fnbEXguR2gnQPzx6rvAdEOdmQH93IGWA1rpADDBw==