Skip to content

Logo

VevoPay

Supports in this guide: Payments, Payouts

Note

No independently verifiable public website could be confirmed for this provider - none is listed in OFT, and no corroborating source was found. Contact your account manager for onboarding details.

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from VevoPay)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from VevoPay

Contact your VevoPay account manager to get your account verified and receive the following credentials.

  • Company ID -> Corefy field company_id.
  • Merchant API key -> Corefy field api_key.

TRY, via several local Turkish payment methods (card, Papara, bank transfer, and others).

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open VevoPay in the provider directory and press Connect at VevoPay Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • Company ID
  • Merchant API key

Success

You have connected VevoPay Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to VevoPay's hosted checkout.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "209a2d42-8bad-4b50-bf27-c8da59b3878e",
      "service": "papara_try_hpp",
      "currency": "TRY",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Wick"
      },
      "service_fields": {
        "identification_number": "21321312234"
      }
    }
  }
}

Important

  • customer.reference_id and customer.name are required for all Payments.
  • service_fields.identification_number is required for the papara_try_hpp service specifically - other services may require different service_fields, depending on the local payment method.
  • customer.metadata.username is sent to VevoPay as the customer's username; if not provided, customer.reference_id is used instead.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "b8f1b6a2-6df3-4041-a083-8572bf055b03",
      "service": "papara_try_hpp",
      "currency": "TRY",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Wick",
        "metadata": {
          "username": "johnwick123"
        }
      },
      "service_fields": {
        "identification_number": "21321312234"
      }
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Refunds

VevoPay does not support refunds.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds via the selected local payment method.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "bank_transfer_try",
      "currency": "TRY",
      "amount": 150,
      "customer": {
        "reference_id": "36544500"
      },
      "fields": {
        "account_number": "TR800004600164888000278881",
        "beneficiary_full_name": "Ilkin Karatekin"
      }
    }
  }
}

Important

  • customer.reference_id, fields.account_number, and fields.beneficiary_full_name are required for all Payout services, regardless of the method.
  • TRY amounts must be whole numbers - a payout with cents is rejected before it's sent to VevoPay.

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1b2c3d4-5e6f-4789-8a02-5b6c7d8e9f0a",
      "service": "bank_transfer_try",
      "currency": "TRY",
      "amount": 150,
      "customer": {
        "reference_id": "36544500",
        "metadata": {
          "username": "Anel Atagay"
        }
      },
      "fields": {
        "account_number": "TR800004600164888000278881",
        "beneficiary_full_name": "Ilkin Karatekin"
      }
    }
  }
}

customer.metadata.username is sent the same way as on Payments (falls back to customer.reference_id if not set).

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Additional info

  1. No active reconciliation on either flow - VevoPay statuses for both Payments and Payouts arrive only via the asynchronous callback; there is no active status request available for this connector.
  2. No recurring - this connector does not support saving/charging a token through Corefy.
  3. No Options or Constants are configured for this connector.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Company ID and Merchant API key
  • Payment stuck pending with no status update -> this connector has no active status request; confirm your callback endpoint is reachable and correctly configured
  • Payout rejected for missing fields -> fields.account_number and fields.beneficiary_full_name are required for every payout method
  • Payout rejected for invalid amount -> TRY payout amounts must be whole numbers (no cents)
  • Refund fails -> VevoPay does not support refunds through Corefy

Question

Still looking for help connecting your VevoPay account? Please contact our support team!