nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Payment 2.0 parts and new PCI DSS requirements

Morag Paterson

Has anyone implemented or developed the appropriate scripts and inventory required for the upcoming PCI DSS SAQ A (6.4.3) update due at the end of March 2025? We use Payment 2.0 parts which ‘pop up’ (aka use iframes) and these are now deemed to require a variety of scripts to ensure security and integrity under PCI. Any thoughts on this gratefully received. Thank you.

Find more posts tagged with

NetCommunity

Comments

David Seager

@Morag Paterson

David here from Blackbaud, we will be meeting the new PCI DSS SAQ A-EP requirements with our NetCommunity software. This will still ensure we are meeting the new requirements while maintaining our payment platform using Blackbaud Checkout.

Katie Rounke

@David Seager
I have a couple questions. We were using 1.0 and were managing the EFT gifts ourselves. With these new requirements we need to change our to payment 2.0. Can you tell me whether we will still have the option to manage our EFT gifts ourselves? My other question is about recurring gifts that were set up on our previous system. Will we need to do anything for those?

David Seager

@Katie Rounke

Yes you can still manage those gifts yourselves. With the new Blackbaud Checkout requirement, the data will still be sent to Raiser's Edge like before, where you can manage your recurring & EFT gifts in a RE batch.