Skip to content

Logo

Pay4funGo

Supports in this guide: Payments, Payouts

Note

No independently verifiable public website could be confirmed for this provider - none is listed in OFT. Contact your account manager for onboarding details.

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

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

Prerequisites: get from Pay4funGo

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

  • Merchant ID -> Corefy field merchant_id.
  • Merchant Key -> Corefy field merchant_key.
  • Merchant Secret -> Corefy field merchant_secret.

BRL only.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

Success

You have connected Pay4funGo Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to Pay4funGo's hosted payment page. Three local Brazilian methods are available, all BRL only: PIX (pix_brl_hpp), Boleto Bancario (boleto_bancario_brl_hpp), and bank transfer (bank_transfer_brl_hpp).

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 100,
      "fields": {
        "cpf_number": "36703436010"
      }
    }
  }
}

Important

fields.cpf_number (the customer's Brazilian tax ID) is required for all three Payment services.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@test.com",
        "date_of_birth": "1990-01-01",
        "address": {
          "post_code": "65001"
        }
      },
      "fields": {
        "cpf_number": "36703436010"
      }
    }
  }
}

Important

customer fields are all optional - if missing, they are simply left out of the request (no hardcoded fallback values are sent), except as noted under Constants below.

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

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

  • LANGUAGE -> checkout page language; defaults to en-US if neither the request nor the constant provides one.

Refunds

Pay4funGo 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 for a PIX payout (service pix_brl, the only Payout method available).

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "pix_brl",
      "currency": "BRL",
      "amount": 150,
      "customer": {
        "reference_id": "cus_456"
      },
      "fields": {
        "cpf_number": "36703436010",
        "account_type": "CPF",
        "bank_code": "15",
        "bank_branch_code": "12345",
        "account_number": "6789",
        "bank_account_type": "personal"
      }
    }
  }
}

Important

  • fields.cpf_number, fields.account_type, fields.bank_code, fields.bank_branch_code, fields.account_number, and fields.bank_account_type are all required for the PIX payout.
  • customer.email and customer.date_of_birth are forwarded to Pay4funGo if present, but are not required.

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1c9f6a0-2d5e-4a7b-9b1e-6a3f0d8c7b2a",
      "service": "pix_brl",
      "currency": "BRL",
      "amount": 150,
      "customer": {
        "reference_id": "cus_456",
        "email": "test@test.com",
        "date_of_birth": "1990-01-01"
      },
      "fields": {
        "cpf_number": "36703436010",
        "account_type": "CPF",
        "bank_code": "15",
        "bank_branch_code": "12345",
        "account_number": "6789",
        "bank_account_type": "personal",
        "beneficiary_phone_country_code": "55",
        "beneficiary_phone_area_code": "11",
        "beneficiary_phone": "987654321"
      }
    }
  }
}

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

Pay4funGo does not support refunds on Payouts.

Additional info

  1. Active reconciliation is available on both Payments and Payouts - Corefy can poll Pay4funGo's status endpoints in addition to receiving its callbacks.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Merchant ID, Merchant Key, and Merchant Secret for the selected environment (test_mode)
  • Payment rejected for missing fields -> fields.cpf_number is required for every Payment service
  • Payout rejected for missing fields -> all of fields.cpf_number/account_type/bank_code/bank_branch_code/account_number/bank_account_type are required
  • Refund fails -> Pay4funGo does not support refunds through Corefy

Question

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