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
- 2f8768965cc2047d3df1195ad5f4960af33e7af836bd8f215ca54fb3fca61436
- request
- 93f098ccba968008329290214649621a3448ad73ea2d0efb9a15105c832cfb0e
- transaction
- 51d5af94deffa561e68593a446916eb387db17fd4182a727d2dd976139b30e83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69953
the chainentry 69953
- sealed to the entry before
- b12d4c9c300b8433f476c08c922c221e9f8e8027a69639a73f1db59349ec4892
- this leaf
- 724a739c75cd160c9f2e8487638be4781642d50a93c4d3fcd8ffbe21e0bcea5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PVnoY9nonZywmtexEGyp6DSMbqJd6f7smvTmoaM7a0Y/praIM8JE9RNmxmnhgStkv/X+snCeLhHeA0jHnffzAg==