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
- 1513fc55f13e3f66b81c6ae0a20e4d77ada0ffa0f6069591eefd32c077d40f8a
- request
- 49414faa8c6484f7db673faa2caa4e93878799de732e224a64521ef815b45e4f
- transaction
- 23248fd55cd7594c68fdc675ab8ae9c1106921c9b427578797d90c4a17b70aaccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42704
the chainentry 42704
- sealed to the entry before
- 388c5dcaa47c2e971f5f5f66bd1b0f8baceca0949e947ca7487220e726961596
- this leaf
- 06a7104ce8d1cd6c4f7fe557ba550cf0970ee54652fd38143ca6716079838767
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1TZEmc4zlK8KIXYPxFCcY8bALZV5VJTc/fbWSH4io5gj2UY2XYeM110n9ccgxwNRxAv6fYe0kuGq4PvJZnT0Ag==