Results for

Results for search.results.searching

Product Overview

Worldline Virtual Pay is a powerful, API-first platform designed to bridge the gap between pay-in and payout processes, especially for businesses in the travel industry. It enables you to programmatically issue single-use or multi-use virtual cards, automating supplier payments and transforming your payment workflows. By integrating Virtual Pay, you can reduce manual reconciliation, optimize your working capital, and create new revenue streams through interchange rebates. Our solution offers a single, seamless integration for both payment acceptance and virtual card issuance, simplifying your entire payment ecosystem.

Why Integrate with Virtual Pay?

Generate New Revenue

Earn significant rebates on supplier payments. Our platform offers a competitive, tiered interchange fee structure, allowing you to turn a cost center into a profit generator.

Optimize Cash Flow

Reduce liquidity requirements by linking pay-ins directly to payouts. Funds are only reserved at authorization, not issuance, giving you greater control over your working capital.

Automate Reconciliation

Eliminate hours of manual work. Each virtual card can be linked to a specific invoice or booking, and our unified reporting provides a single view of both pay-in and payout transactions.

Enhance Security

Reduce fraud risk with single-use virtual cards. Set precise controls on each card, including spending limits, valid merchant categories, and expiration dates.

Increase Supplier Acceptance

Leverage our wide range of VISA card products with multiple interchange tiers. Our 3DS frictionless enabled cards are designed to boost acceptance rates with suppliers.

Simplify Integration

Get up and running quickly with our RESTful B2B Payout API. Our modern, well-documented endpoints make for a smooth developer experience.

Feature Capabilities

  • Virtual Card Issuance: Instantly create virtual debit cards via a single API call.
  • Full Card Lifecycle Management: Programmatically issue, block, unblock, and deactivate cards.
  • Dynamic Card Controls: Set specific limits for each card, including total transaction amount, number of transactions allowed, and validity period (start/end dates).
  • Real-time Balance Information: Retrieve account balances for multiple currencies (EUR, USD, GBP) at any time.
  • Transaction History: Fetch a detailed list of all transactions associated with a specific virtual card.
  • Supplier Management: Manage a directory of your suppliers directly through the API.
  • Merchant Category Code (MCC) Controls: Restrict card usage to specific merchant categories for enhanced security and policy enforcement.
  • Unified Reporting: Link payout transactions (virtual cards) to their corresponding pay-in transactions for simplified reconciliation.
  • Secure Card Detail Retrieval: Securely fetch sensitive card details like PAN and CVV when needed.

API in Action: Issuing and Using a Card

Here’s a practical example of how to issue a virtual card for a specific supplier payment and then retrieve its details.

Step 1: Issue a Virtual Card

Make a POST request to the /api/v1/merchants/{merchantId}/cards/issue endpoint. Include a unique VCP-Idempotency-key header to prevent duplicate requests.

Request Body:

{
"cardLimitAmountInMinorUnits": 10000,
  "currency": "EUR",
  "numberOfTransactionsAllowed": 1,
  "cardProduct": "VISA_DEBIT_EUR_IDX_200",
  "supplierName": "Grand Hotel",
  "merchantReference": "Booking-INV-56789",
  "payinReference": "JL9XDD2024ZGU8Q",
  "validityPeriod": {
    "startDate": "2025-07-01T00:00:00Z",
    "endDate": "2025-07-31T23:59:59Z"
  },
  "recipientEmailAddress": "payments@grandhotel.com"
}

Response (201 Created):

{
  "cardReference": "672df5b0-48b3-445a-95a6-a520ab437611",
  "pan": "424242******4242",
  "expiryDate": "1127",
  "startDate": "2025-07-01T00:00:00Z",
  "endDate": "2025-07-31T23:59:59Z",
  "cardLimitAmountInMinorUnits": 10000,
  "currency": "EUR",
  "numberOfTransactionsAllowed": 1
}

Step 2: Retrieve Security Code

To complete a "card-not-present" transaction, the supplier may need the CVV. Retrieve it securely with a POST request to /api/v1/merchants/{merchantId}/cards/{cardReference}/card-security-code.

Response (200 OK):

{
  "cardSecurityCode": "123"
}