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
- e533db122d7af4c4f96aa7adbe975942de86be3d1797573c77e4009d4639e79b
- request
- 04e9379794a9fe53c6c86928f0e7be484326baf77f2c05b0b2f4a5ee66597748
- transaction
- ca7c6dee5b3d274445db603c75f776151386f0f7c03182201968b8a32aa66d5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 586
the chainentry 586
- sealed to the entry before
- 7a41ace044325b54a7b00fc5c930cf32c1e83580b455f969f82648e90dadc736
- this leaf
- 0be03cdf34bde7293b1907139c30df8d977d70b4d64d8753bd62e35ec9b2289c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3UkMCb8T/L9OsqdkTabjHUwdJYq0ZalvJBSBpiL5UPNZI4N2Lel7bNhA2I8K0nW6v/QH5oCNLp009V9MHCjzCQ==