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
- 527f65924b75c2a590c75a1b74cc2f0cd8aa65a77a507cf84d087e150fba1cfd
- request
- 3d09961ad0e35f2a147ab2ab88961737da7c7cae00988c0b7dedc83293c416fc
- transaction
- 4152c4253389c0d2b87eeeb5da416da444bfd5246532d0488571bfff5c15d56fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34752
the chainentry 34752
- sealed to the entry before
- 27419081946649313c3ecc59323f97e9a90a1a254e79bbdef98949ce777474b9
- this leaf
- 9190ed7f66951748e7b56d013ccfc4dce13ef69ce003717054289fe08abbbbf6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ywd6kWqB9q3hUsJxzasDr3nj+1rKUzQDV3Gah0VT87K1BXHBTDOZH6xkhoH4J9xXnRiDPC23zjs9RTXragdPDQ==