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
- e119af2eba367c953d2bca0b82d4c1931f3332fffa7249da2aa354a3fbc1b97d
- request
- 8d5fc718f615174a9549ba17f154d4497a67f78c82668fd4088f629c03dd1bb6
- transaction
- a1f71e3cea53cec582b6be4eac3b361684d9d7df8c3e85931031915695af788bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45270
the chainentry 45270
- sealed to the entry before
- 8505660c65d6297c7f363571247892a1c334109d102b7d608cc01ad75001660f
- this leaf
- 78ca6110221f903158e40d7ef30f94cf6f68a75217a02af641cf8ed88488f777
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jLBiT4lh2MnJmpBRjug52HVAC4mbzfh23aAQOYyVnVFhjbncQDt5JLsP9B5LlGWRKwF364BJkuZ2DeybbcojAg==