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
- d27ffc52f09bd3efe2fc612790cf09a7fcefa53fbf56064ebd54400d05117cee
- request
- ebf9598ed2aaad841e96f936698cda06da67082f4cdceea8b066509e0ab458c4
- transaction
- b9ebfcba3c2e2635643b56d40dfbb0b1321353d30ff9f897a69c9acf90c743c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60010
the chainentry 60010
- sealed to the entry before
- e721609e42b6146e631c885a56c8dd03b7eebb62119b44446e9861c9c601b9e6
- this leaf
- a0ef1e861bc83dd70f14ec67132fa7b2f034f6a0dd4fa5f1a8fb7372749c09a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2VwJEaSHWICAgRpnPwuJqNHxCdcCtVwFHvf5C+JxSaWi8wywGJLSnlmOLpTccmpwRum/YKyV+i1bwMPKUZA4CA==