Skip to main content
GullySystem
Payments · PayPal integration

Match PayPal orders, refunds and disputes to the sales records in your own software.

PayPal collects payments from buyers who prefer it, but the sale itself is recorded elsewhere; the connection between your PayPal business account and your software is our build. Checkout orders and captures update the sale, refunds start from your side, and disputes reach the right person. Scope depends on your account.

At a glance

Connecting PayPal to the rest of your business.

A seller who accepts PayPal often keeps two lists: the orders in the shop or back office and the transactions in PayPal. Matching them takes time. A refund done in one place goes unnoticed in the other.

The link carries PayPal activity into your order, invoice and customer records, while PayPal remains the place where buyers pay. What is available depends on your business account type, your country and the API access granted.

What moves

What flows between PayPal and your system.

Each flow is agreed one at a time: which record, in which direction, and what happens when it fails.

Checkout orders confirm the sale

Once a buyer approves a PayPal checkout order and it is captured, the matching order becomes paid and keeps the capture ID and the buyer’s PayPal email. The sale is closed.

Authorisations held, then captured

For goods shipped later, an authorisation is placed first. Dispatch in your system then triggers the capture so that a buyer is charged only when stock has left the warehouse. Shipping decides billing.

Refunds started from the return

A return accepted in your software raises a full or partial refund against the original capture; the refund status comes back to close the credit note. No second login.

Disputes routed to a person

When a buyer opens a dispute, a case appears on the related order with its reason and deadline. Evidence such as proof of delivery can be attached from your own records. Deadlines are visible.

Payouts and fees reconciled

PayPal balance activity is read with its fees and currency conversions, so accounts staff can see which orders make up each withdrawal to the bank. Fees are not lost.

How it is built

From scoping to hand-over.

1. Scope the objects and direction

Orders, captures, refunds, disputes and balance transactions are the PayPal objects we weigh first, and each is marked read-only or writable from your software. Scope stays narrow.

2. Connect and test in the sandbox

PayPal provides a sandbox with test buyer and seller accounts, and we run approvals, refunds and a staged dispute there before any live credentials are added. Live credentials come last.

3. Cover captures, disputes and payout fees

Notifications can repeat, so each one is recorded once by its ID. A payment with no matching order goes to a queue where a person links it to a sale or flags it.

4. Match settlements, then hand over

Each day a report sets PayPal activity beside your orders and refunds. The handover pack holds the credential renewal steps, the queue procedure and the notification types in use.

Common questions

Questions about connecting PayPal.

Does information move in both directions?

Yes, where it helps. PayPal reports payments and disputes to your software, and your software can start captures and refunds; each field has one owner so edits do not collide.

What does my PayPal account need to have?

A business account with API access, in a country where the features you want are offered; we confirm this against your account before any scope is agreed.

Can earlier transactions be imported?

Often, within what PayPal’s reporting lets us retrieve for your account; we match those transactions to existing orders and list any that cannot be matched.

What happens when PayPal changes its API?

We isolate the PayPal code in one module so that a change affects one place; a support arrangement includes reviewing announced updates and revising the mapping.

PayPal remains the trademark of its owner. The connections to it are our own work, and we are not affiliated with the company.

Start with your requirements

Tell us how you use PayPal.

Share your requirements and an engineer will read them before getting in touch.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements