Requirements

Home
Getting started
- About Connect
- Basic principles
- Integration methods
- Operating models
  - Full service
  - Gateway service
- Go live
Payment methods
- By country
- By payment product
- Beta programs
Accepting payments
- Payment scenarios
  - One-off payment
  - Refunds and cancellations
  - Installments
  - Single-click payments
  - Recurring & Subscription
  - Merchant initiated transaction
  - Authorization reversal
  - Tokenization
    - Card on file
    - Account Updater batch
    - Account Updater token
    - Direct Debit mandate
- Compliance
  - Privacy and Data Protection
  - PCI DSS
  - PSD2
- Handling multiple currencies
- Fraud management
  - Address verification (AVS)
  - Bank account validation
  - Card-not-present fraud
  - Card verification value (CVV)
  - Device fingerprint
  - Fraud risk triggers
  - Fraud status codes
  - Test scenarios
  - --- Line separator ---
  - ACI Fraud Prevention
  - Microsoft Dynamics 365
  - 3D Secure
    - Dynamic 3D secure
    - 3D secure version 2
    - 2-step 3D secure
- Smart routing
- Mobile
  - Top 10 tips
  - Mobile payments
- Industries
  - Industries
  - Digital
  - Gaming
  - Retail
  - Travel
Testing
- Test card generator
- Sandbox access
- Test cases
After the payment
- Refunds
- Chargeback handling
  - Dispute
  - Soft descriptor
  - Return policy
Developer tools
- Two-factor authentication
- API Explorer
- Ordering of payment products
- Configuration Center
- Integration Dashboards
- Hosted payment pages
  - Shopping cart
  - Subscription details
- SDKs
  - Mobile and browser SDKs
    - Android SDK
    - iOS SDK
    - Swift SDK
    - JavaScript browser SDK
    - Flutter mobile SDK
  - Server SDKs
    - Java SDK
    - PHP SDK
    - Node.js SDK
    - .NET SDK
    - Python SDK
    - Ruby SDK
    - Go SDK
- Full API references
  - Server API
  - Client API
- API versioning
- Error handling
  - Response codes
  - Error codes
  - Managing exceptions
  - Idempotent requests
- Webhooks
  - Event types
  - Event structure
- Plugins
  - Magento 2
    - Overview
    - Payment products
    - Requirements
    - Installation
    - Configuration
    - Workflow tips
    - Release notes
    - Troubleshooting
  - VTEX
Reporting
- Secure file transfer
Blog
- Trending
Support
- Release Notes
  - Highlights
  - REST API
  - MyCheckout Hosted Pages
  - Webhooks
  - Server & Client SDKs
  - Other
- Old release notes
  - Overview
- FAQ
- Contact
API Reference
- Boarding
- Merchant Boarding Portal
- Pre-production/sandbox access
- Configuration Center
- Payment Console
- Production
- Configuration Center
- Payment Console
- Insights
Switch color mode Theme

Results for

Results for Searching

Before you begin installation or update

Create a backup of the shop’s database and files to ensure all important information is safe and sound
Give the plugin installation and functionality a once-over on a testing system to confirm it works as expected

Requirements

PCI SAQ A-EP compliance (for inline payments), or PCI SAQ A (for other payment types)
Worldline's plugin v4.X supports Magento 2.4.5-2.4.7
PHP 8.1 and 8.2 version
Worldline account (please contact us for more information)
Composer