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
- 3730c30ad2276524a67f78f76b9c4d7574ade3db347769e9cf84caf11dd16f75
- request
- 6566b9bfa75d7c30f77a393c06aa0f2e659ee8e2ceecbfdf1e59e0ac52328f44
- transaction
- f56159fe2278033c452d7eb6da9f8c991f89c8c1bc13844fac990a0ba7427efccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23109
the chainentry 23109
- sealed to the entry before
- d950408744620d888a3f605457c8aa2cf28057504fad3e3275d7bd5f864e7082
- this leaf
- 7159cce2b583a2886ac81a8b0b47b0ecc87216066648a38ce161b62809b0fc3a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BvlxMM/vV9+7OcfFd3/d6zHT8IbXatTEdFCYKQFEVqValRrIKJ4Vy3AezyAbpj5BapR1B4PEiZgCZr3ghn6MBQ==