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
- f3e2461712f54df86f577e3f0ff5a29964bc44a8d46def2864cfa0343e71182b
- request
- 503da76e16ce73e5aaa436c44e1aaf8a817f328018d46232ce06fa9ecb0ee39b
- transaction
- b2906e1fb093af451c51b71b5364701623e060385e0bb84e0505bb722e7c1d47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2405
the chainentry 2405
- sealed to the entry before
- ada4c739b49eaec664916d9ebdc6d45b30bb670d2ae36743a18fbd4dc94fb11e
- this leaf
- 6e979b8564b23beb83f2662b06596d15b55f9436b27f7e912ae8b094d3fa5f29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dk7JW8onQerhBgQEcZRg+NSDhXVvsFfM0nyHgw0/7S/cUVTfW0qzMc5q5wnkFC6DJviS499kZBUEWBWxmHx+Ag==