Global Payments
Keep Global Payments in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
27 ways to read, 3 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Global Payments, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create payment linkApproval by rule
- Create payerApproval by rule
- List merchant accountsRead
Example flow
- Global Payments · List merchant accountsDone
- Global Payments · Create payment linkNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Global Payments.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Global Payments
- Global Payments's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Global Payments test account before you go live.
For developers
Technical detail
GP API: transactions, refunds, settlement, disputes, stored payment methods, links, payers, batches, transfers, accounts, merchants and reports; writes only for payment links and payers.
Global Payments API docs- Source actions
- 27
- Destination actions
- 3
- Data types
- 16
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Accounts2
- Get merchant accountSource
Get merchant account by ID.
- List merchant accountsSourceIncremental
Accounts configured for the merchant (transaction processing, data services, disputes, tokenization, funds) with permissions, countries, channels, currencies and payment methods.
Actions2
- Get API actionSource
Get API action by ID.
- List API actionsSourceIncremental
Audit trail of GP API requests: type, resource, result and app.
Batch transactions1
- List transactions in a batchSource
Sales and refunds in one batch with amounts, tax, gratuity and reference.
Batches1
- Get batchSource
Get batch by ID.
Deposits2
- Get depositSource
Get deposit by ID.
- List depositsSourceIncremental
Daily deposits with sales, refunds, chargebacks, reversals and fees totals.
Disputes2
- Get disputeSource
Get dispute by ID.
- List disputesSourceIncremental
Disputes with stage, status, reason, amount and response deadline.
Links3
- Create payment linkDestinationNot retried automaticallyApproval before production
Create a pay-by-link URL for an amount; the customer still has to pay. Nexra does not send the link by email or SMS.
- Get payment linkSource
Get payment link by ID.
- List payment linksSourceIncremental
Pay-by-link links with status, amount, usage and the transactions made through them.
Merchants2
- Get merchantSource
Get merchant by ID.
- List partner merchantsSourceIncremental
Merchants in your partner program with status, name and currency.
Payers4
- Create payerDestinationProvider duplicate protectionApproval before production
Store a customer and optionally link existing stored payment method tokens.
- Get payerSource
Get payer by ID.
- List payersSourceIncremental
Stored customers (payers) with name, reference, email and linked payment method IDs.
- Update payerDestinationProvider duplicate protectionApproval before production
Update a payer's name or reference, or its linked stored payment method tokens.
Payment methods2
- Get stored payment methodSource
Get stored payment method by ID.
- List stored payment methodsSourceIncremental
Tokenised payment methods with brand, last four and expiry; card numbers are never returned.
Refunds1
- List refundsSourceIncremental
Refunds already processed (transactions of type REFUND), filtered by creation date, status or currency. Nexra never issues refunds.
Settlement disputes2
- Get settlement disputeSource
Get settlement dispute by ID.
- List settlement disputesSourceIncremental
Disputes that affected deposits, with financial impact. Requires acquiring with Global Payments.
Settlement transactions1
- List settlement transactionsSourceIncremental
Transactions included in deposits, with deposit and batch dates. Requires acquiring with Global Payments.
Transaction summaries1
- Get transaction summary reportSource
Aggregated sales and refunds across payment methods, with a breakdown by category and brand.
Transactions2
- Read UCP transaction statusSource
Read an existing transaction: status, amount in minor units, order, batch, masked card and acquiring system.
- List transactionsSourceIncremental
Sales and refunds processed recently, filtered by date, status, type, reference or batch.
Transfers2
- Get transferSource
Get transfer by ID.
- List transfersSource
Transfers between merchant fund management accounts (read only).
Access and limits
- Authentication
- UCP read-scoped access token
- Plans and access
- A Global Payments API (GP API) app with an access token that has reporting permissions. Settlement reporting (deposits, settlement transactions and disputes) is available only to merchants who use Global Payments as their acquirer. Some reports need live configuration.
- Test environment
- Create an app on developer.globalpayments.com and use apis.sandbox.globalpay.com.
- Rate limits
- GP API returns HTTP 429 when limits are exceeded; Nexra honours Retry-After with bounded retries.
- Pagination
- Lists use page and page_size (up to 1000) and stop when a page comes back short.
- Provider events
- GP API sends status notifications to the URL configured on the app or request. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Writes are limited to creating payment links (the customer still pays) and creating or updating payers. Intentional exclusions: sales, refunds, reversals, captures, increments, adjustments, reauthorizations, confirmations, splits, holds and releases; dispute acceptance or challenge; payment method create, edit, delete, detokenize or cryptogram; transfers and transfer reversals, funds, payouts and batch close; payer delete; merchant and account create or edit, merchant documents; device orders; installment plans.
- Payment links are always type PAYMENT with channel CNP; link functions that fund payout cards or move funds, payer details and email or SMS delivery are never sent. Link creation has no documented idempotency key, so it is never retried.
- Merchant persons, addresses, tax IDs and bank details are not mapped; merchants.list needs a partner program. Payment links and the transaction summary report depend on live configuration.
- Access tokens are obtained outside Nexra and must be replaced when they expire; app-key token exchange is not automated.
- Lists filter by creation date only; there is no last-updated filter, so incremental reads pick up new records but not later status changes. Settlement lists filter by deposit date.
- Fees: GP API reports fees as deposit totals (feesAmount on deposits); there is no fee list endpoint, and per-transaction fees are not mapped.
- Card first six digits, holder names, network tokens, bank routing details and dispute documents are not mapped.
Developer reference
- Create the Global Payments credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Global Payments, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/global-payments and the Connections API.