Starpago

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• App ID
• App Secret
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice. Starpago supports Pix in Brazil (BRL) and PSE, Nequi, and BReB in Colombia (COP); the exact fields needed depend on the method - see below.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 10
    }
  }
}

This connector also supports pse_cop_hpp, nequi_cop_hpp, breb_cop_hpp (all COP), as well as pix_brl_invoice (a direct-invoice variant of Pix, instead of a hosted-page redirect).

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "cpf_number": "12345678900"
      }
    }
  }
}

customer is optional - customer.name is used as the payer's name if present; otherwise Corefy falls back to fields.payer_first_name + fields.payer_last_name (Pix only, both required together for this fallback).

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

No Constants are configured for this connector.

Options

• finalize_after_minutes -> optional, number - if a reconciliation check still shows the payment pending this many minutes after it was created, Corefy gives up waiting and reports it as a timed-out failure instead of checking indefinitely. Configured per payment method.

Refunds

This connector does not support refunds.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds via Pix (Brazil) or bank transfer (Colombia, to a wide range of local banks and wallets - Bancolombia-network banks, Nequi, Daviplata, Movii, and more). The exact fields required depend on the destination - the Dashboard shows them once a method is selected.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "pix_brl",
      "currency": "BRL",
      "amount": 10,
      "fields": {
        "cpf_number": "12345678900"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "pix_brl",
      "currency": "BRL",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      },
      "fields": {
        "cpf_number": "12345678900"
      }
    }
  }
}

customer.name is forwarded as the recipient's account name; customer.email/customer.phone are forwarded for bank-transfer payouts in Colombia.

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

No Options or Constants are configured for this flow.