Worldpay
United States / United Kingdom / global: read latest payment event.
Match provider records to your invoices, orders and finance workflows without moving funds.
Source actions
1
Destination actions
0
Data types
1
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
payments
- Read latest payment eventSource
Follow an existing Worldpay events link on the selected origin; never executes payment actions.
Authentication
Access Worldpay Basic credentials
Plans and access
An approved provider account with API access and the required read scopes. Availability depends on the merchant country, product, permissions and provider agreement.
Test environment
Use dedicated provider test credentials where available; credential-backed validation is pending.
Rate limits
Provider/account-specific limits apply. HTTP 429 and Retry-After are handled with bounded retries.
Provider events
Provider events are not ingested by this adapter. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Pinned Access Worldpay v5 events read contract; events may lag by up to 15 minutes. New Payment Queries API is separate.
- Supply the payments:events link from an existing provider response. No authorisation, settlement, cancellation or refund calls.
- Credential-backed validation pending.