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
- 1389b82abe11de5ea2dfdbad4919bb422dd3ec2113be07f6273937e98bf27881
- request
- f4db39de04d1ad252809779643077835a0437d499c19b1200eb9e25ed5cdb48e
- transaction
- 25fc803d2ed57ce264af22abb15b2916e612a004b9aaef19dc13ec244aba71c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29386
the chainentry 29386
- sealed to the entry before
- 824bd5e1a0c5bc23684c11277e9aef38c920dc73c6d456f82adbb66711ad8db7
- this leaf
- 9b84d9646b3aef456148b21a4e3baa1bc253c0a0067289efc2ab4bebfc9dbd19
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Z+zd+fXkKOnQsIlOv7sfHvThBT8fZb+CMKrpUbIiqGV5W1ux9Qhw6oLVfb3gz2WJ7boxGJj/rFWf5Df6NqkAQ==