Skip to content

Logo

Payelu

Manage your Payins & Payouts in LATAM - seamlessly receive and send payments connecting to local payment methods with a single API.

Supports in this guide: Payments, Payouts

Provider website: payelu.com

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

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

Prerequisites: get from Payelu

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

  • Auth point ID -> Corefy field auth_point_id.
  • API token -> Corefy field auth_api_token.
  • Active service -> Corefy field active_service -> optional; identifies which of your Payelu-side services this connection uses, only relevant if your Payelu account is scoped to a specific service.

Available local payment methods (by country): bank transfer (several LatAm countries), SPEI (Mexico), Pix (Brazil), Pago Movil (Venezuela), PSE (Colombia), Webpay (Chile). The exact set of services available to you depends on your Payelu account configuration.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Auth point ID
  • API token
  • Active service -> (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Payelu Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice. Payelu's own services are auto-discovered per account rather than fixed in advance, so the exact service codes available to you depend on your account configuration - the example below uses a representative bank-transfer service.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "bank_transfer_pen_invoice",
      "currency": "PEN",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "bank_transfer_pen_invoice",
      "currency": "PEN",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "individual_tax_id": "45465055"
      }
    }
  }
}

Important

  • customer.name and customer.individual_tax_id (the payer's tax/document ID) are sent to Payelu when provided, but are not enforced by Corefy itself - whether Payelu requires them depends on the specific service.
  • For the spei_mxn_invoice service specifically, customer data is not sent at all - only reference_id, amount and an expiry timestamp.
  • The Venezuela bank-transfer/Pago Movil services (bank_transfer_ves_invoice, pagomovil_ves_invoice) instead pull the payer's bank/phone/document details from account-level Constants (see below), not from the customer object.

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

Options

  • disable_reconciliation -> optional, boolean - when enabled, Corefy does not run active status reconciliation for this connection and relies only on Payelu's asynchronous callback.
  • reconcile_after_callback_minutes -> optional, number (1-7200) - delay before an active reconciliation request is allowed after a callback has already been received.
  • finalize_after_minutes -> optional, number (60-7200) - time after which a payment still pending is finalized automatically.

Constants (fallback fields)

Constants apply only to the Venezuela bank-transfer and Pago Movil services (bank_transfer_ves_invoice, pagomovil_ves_invoice) - they are not a general fallback mechanism for other services.

Currently available constants (Venezuela services only)

  • BANK -> payer's bank
  • RIF -> payer's Venezuelan tax ID (RIF)
  • PHONE -> payer's phone
  • BENEFICIARY -> beneficiary name

Refunds

Payelu 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. As with Payments, the exact service codes and required fields depend on the destination country/method - the example below is representative of a bank-transfer payout.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "bank_transfer_pen",
      "currency": "PEN",
      "amount": 150,
      "fields": {
        "account_number": "12345",
        "bank_account": "12345",
        "bank_code": "123",
        "beneficiary_name": "John Doe",
        "beneficiary_document_id": "AA1234",
        "sender_full_name": "Test Sender"
      }
    }
  }
}

Important

The exact required/optional fields keys (account type, document type, beneficiary city, etc.) vary per destination country and bank - confirm the current set for your target method with your Payelu/Corefy account manager before going live.

Options

  • disable_reconciliation -> optional, boolean - when enabled, Corefy does not run active status reconciliation for payouts on this connection and relies only on Payelu's asynchronous callback.

Refunds

Payelu does not support refunds on Payouts.

Additional info

  1. Active reconciliation is available on both Payments and Payouts unless disable_reconciliation is enabled, in which case status updates arrive only via Payelu's asynchronous callback.
  2. No hardcoded fallback values - missing optional fields are simply left out of the request to Payelu; the only exception is the Venezuela-specific Constants described above, which are merchant-configured, not fake defaults.
  3. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Auth point ID and API token for the selected environment (test_mode)
  • Service not available -> the set of services is tied to your Payelu account configuration; confirm with your Payelu account manager which services are enabled
  • Payout rejected for missing fields -> required fields differ per destination country/bank; confirm the exact set for your target method
  • Refund fails -> Payelu does not support refunds through Corefy

Question

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