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
- f7c821ab3bed7046b4a2f2a86ba614629a72080d694539c0751d5615a992e6dc
- request
- 630032c1db66acacef71aab2c6b27e91a2a3497d4998b39f191604c751b7daf9
- transaction
- a73960047e4fe8d94b71f74b3fe91dcb139ca6ba509a624cbeda6cdd245de879computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11587
the chainentry 11587
- sealed to the entry before
- 2fffe70998655afa2ee9dcb795401d4cf46f07f1047c7d32e0b651ed3a8dcc83
- this leaf
- e8c091eedb9eab8e39708664f24c0d3eb2734c8306d95874b4db63e062e51ad4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Va5d8BCoCjnteg7wxTg58z/QN2o1JH8B2PGW1b8YGokPS+LchpNnnPGqUUovc0Q7LoEsLhT45sFTWGauJS7yBw==