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
- 06fd582fb4102365b100bd08a0e7ddc019387714ef969259d7e31712fba9d144
- request
- b197b568e01bbeddfccd3db856f6c17f84d086bde183b04d899b2749f5685fa1
- transaction
- 1064dfe4b1dc6dafd31cc0bfaaef0a8e5981f8ab43407babffe616129a771f3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41456
the chainentry 41456
- sealed to the entry before
- 1f5b6f842575ad9e5962be08dc363d1a73089dca8357db84f242c55946fb32f1
- this leaf
- 0a86315db9564d5e871bd37befa4b4b6c3ff73769982c498685163ed732ab98a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- taZSnC2329d47XEKePRrieslzADq6b1XGgVdtyy0zXLXtagxsXfTJ6MtdVfksrE2Xcywy35kix5sYwFSAALgAQ==