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
- 4a843fec3c2f422333dadb4ffdb887d8ecd26b9ddc9740f5f75105836991ae1d
- request
- ddc97f259cbf4d81a9f73b1567da304eeae74488e155ae59fb2767d1b45bb951
- transaction
- 75baeda379d814861ba41b7ba655b011706a8b5dbcf124dca5efceeeb56100cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48560
the chainentry 48560
- sealed to the entry before
- 2dd6a45d3902a4ff87e3d8c24f30e66678b9eadde2c84fad3a7a40ec0d59f954
- this leaf
- 6493dc19ad587b63e92093b4bb219addf7d06627624f8086cea5926acce0c8a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GjeIzIjbzjAOPBKn/kMgBczPjlR1XpZM+0rWt/tflGWD2R6+03sXogb2jv7gUOM3Q/pLI57I4ZYqL5PPcneIAw==