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
- 24f646f15be599e9102dc869bbafdf48e04f8883d9af166e4b4badaa08ac3d8a
- request
- 36cfba01f9803915187a6943ae3ace1ee7110499990a597db1166f6b32a9d966
- transaction
- 4092d3d60293f8e6f85d2a0e808bac9584bb4fa75d232d1af358738486943892computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62141
the chainentry 62141
- sealed to the entry before
- 3be53e1130daf6610ac9159e63d759a3daadc717d2e38372e22cef5023564d44
- this leaf
- e08ee4782ca0196bc42876763935a2efafe8d7318f39015a37ba5282362dd60e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wkst8+XAlze5uKXS1qiP+of+pae2sohv2IlSZU56MximpqDRzY5aco5KXYm8aXH1+fto926OgjvTiJ3kta1XAw==