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
- 6748580e1450c1dc522142a7b2b4463038cf6e190bd19482a4e5f00c9001ea2b
- request
- d238519c5bd583671c1b00ce2ac43e1182061ec93d65838d4d5c99ee79784ff9
- transaction
- 962f32247651618b3e18f191793e39fe8232acf7dd13b901c3de82fb4bb708c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62105
the chainentry 62105
- sealed to the entry before
- d6c3fa8069cb69a6d2854cf46ae2d713cb711ffbbd3129dfca249633583a1b29
- this leaf
- 8fc038a49557fb6aded7ea0cbddae748643c3fd4ac0a26ec5074b6fa7bfcbaa8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pT6vfArT3A/sr0ElSEWHmN5RMxUoXU/6H0oRsvS+nf6i1XD2521pNbcnRuga7ri8uh4bNp3x5ZrWA8l3rI7IBQ==