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
- a893ad67bf7747f0b8d85df37519699b9cfd1976d12139406b8fe0c4fa5226bb
- request
- 497fcfbceafa8a838abd45508edcf0fe02c0bf5285244170f1e34dcdeb4fc7ac
- transaction
- 597beb4ade83c512fa2dd2f01175f1616505d2293740a6fdda568c83b025c353computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33936
the chainentry 33936
- sealed to the entry before
- 8d466fed39b1a969c822839e954d1220c96347f2b09da327e4b056277d5737a8
- this leaf
- 748390f1e6c48724e081c0632d14f3aa2ebff301bd1fbd1e19c00cdd1d328c57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jOg+SRTwDsJtOozeKvP/uBxHGOU3GNkEl8MwyHj/dkWILmLcBMEO+IW8UE6VLBDZ3P6HuVVy8kedVrUf5UmJBw==