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
- 26dcc99015cfe27c58b1dc1c553d955c6c87b8a039baa5b594d8ce1e7238d20a
- request
- 7afe25188322c563795cef3bada2c8d41ee8e9a04f9874211fa965ae4d46d7f8
- transaction
- 850ed390ef3a975203b37b040f02729ef6ddfbc636f5899bda93ac82482f8357computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67617
the chainentry 67617
- sealed to the entry before
- b3fb281e30c1b999e70fd0b2709af8ae0cbc9313ec62a992b34cf911baee02ad
- this leaf
- 2cb6f7ee93b445ac8e8f6cdfd33db7ade98eea12bcdf9ffa73e9c1c809e0c513
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KkILOeHJmfjrenN7Y+DESLz4zT92Bl2UFI/tBgZqpLf+M3PYql6zZJE//eM45eHgmsF1SDg8qOr5gjN94NkWAg==