We connect GiveWP to Global Payments, so donations made on your WordPress forms are charged through your own Global Payments account. GiveWP keeps the forms, donor records and receipts. Each donation carries its Global Payments transaction ID, and the result Global Payments reports sets the donation's status in GiveWP.
A few clients we’ve worked with
Norml builds and tests the gateway that connects an existing GiveWP site to Global Payments: card payments on your donation forms, status updates, recurring gifts, receipts and refunds. Choosing a payment provider or building a new donation site is separate work.
The work covers the payment layer between GiveWP and Global Payments. Donation forms and donor records remain in GiveWP, and each part below is tested in the Global Payments sandbox before live donors use it.
Global Payments appears as a payment option on the GiveWP forms you choose, and donors enter card details in fields Global Payments provides, such as its hosted fields, where your account offers them. The gateway runs on your organization's own Global Payments credentials.
Each donation is marked pending, complete, failed, cancelled or refunded in GiveWP according to what Global Payments reports. Some outcomes arrive after the donor has left the page, so we confirm how your account sends status notifications, and the site checks that each one is genuine before it changes a donation.
Every donation stores its Global Payments transaction ID alongside the donor record in GiveWP, so your team can look up the same payment in both systems when a donor asks about a charge.
For monthly or annual giving through GiveWP's Recurring Donations add-on, GiveWP keeps the subscription and records each renewal as its own donation with its own Global Payments transaction ID. A failed renewal is marked in GiveWP, so your team can follow up with the donor.
We check that the donor's receipt goes out only after Global Payments confirms the payment, and that a declined payment or a repeated notification sends none.
Whether refunds can run through the Global Payments API depends on what your live account allows, so we confirm that first. A refund issued in GiveWP is then sent to Global Payments and shown on the donation. If your team refunds in Global Payments instead, we agree how that change reaches the GiveWP record.
The Yellow Blue
A donation site for a nonprofit supporting Ukrainian families. Its donation flow takes one-time and recurring gifts, issues tax receipts and lets donors change their card or amount, or cancel, on their own.
Wealth by Real Estate
Sales funnels for a real estate education company. Each high-ticket course has its own sales page, and buyers can choose installment payments at checkout.
“Norml Studio's professionalism and responsiveness were impressive.”
“They were proactive in suggesting improvements we hadn't considered.”
“They delivered what they said they would, on time.”
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
An administrator account on the site that runs GiveWP, and a staging copy where the gateway is built and tested before live donors see it.
The Global Payments product your merchant account uses, sandbox credentials shared through a method we agree on, and confirmation from Global Payments of what your live account allows, such as API refunds and stored cards.
Which forms take card payments, whether donors can give monthly or annually, and what a donor should receive after a gift.
Someone on your team who reviews failed payments, refunds and anything the integration cannot match, and who signs off the test results before launch.
We confirm which Global Payments gateway and API your account uses, check for a maintained connector and agree which features the live account will use.
We write down which Global Payments result sets each GiveWP status, how renewals and refunds are recorded, and who receives exceptions.
The gateway is built on a staging copy of your site connected to the Global Payments sandbox, so no real card is charged during development.
We run approved and declined payments, a repeated notification and a refund, plus a renewal and a cancellation if you offer recurring giving. After each one we check the donation, the donor record and the receipt, and you approve the results before launch.
We switch the gateway to your live credentials, check the first live donations with your team and hand over notes on statuses, notifications and exception handling.
No account layer between you and them. These are the Norml specialists this work runs through.
DevOps & Backend Developer
Full-Stack Developer
Founder & Architect
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
