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
- 435feec5d47582766dc79b832ee4a35c6a9de476823d3c710b443f5a843cdef9
- request
- 607a1c0f6b9f689185ec10e5eef6e8a5f6ec918e51bd18f387c645595ba5d50b
- transaction
- b43a16cb8d802857c8a35fccdf8ecd9da1ed4a4192e06218b2056f19874952b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17620
the chainentry 17620
- sealed to the entry before
- ea4acfcf3e92b7711ea219beb72120e21bac1a131812bbbf427d5ffc2504683d
- this leaf
- d194d6d2c9b625886403adfd7eb98c9a3cf0da0e278c2a61e077cb2904aa4b71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SX89xPXj7udAJfG1fNl4YKW0kTsR1zxYnwjnCbSYze0Q68ye2ovU+nziUNKT2htX8p2xcAt0emOYXF91IAeCBA==