Skip to content

Logo

SmartFastPay

Your payment intermediary specialized in Latin America

Supports in this guide: Payments, Payouts

Provider website: smartfastpay.com

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

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

Prerequisites: get from SmartFastPay

Contact your SmartFastPay account manager to get your account verified and receive the following credentials. One Provider account connection covers both Payments and Payouts.

  • Client ID -> Corefy field client_id.
  • Client Secret -> Corefy field client_secret.
  • Webhook Secret (optional) -> Corefy field webhook_secret -> used to verify callback notifications from SmartFastPay.
Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

Choose Currency / Features; check with your Corefy account manager which methods are enabled for your account.

Success

You have connected SmartFastPay Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice. Pix, Pix QR, and (optionally) Nequi redirect to a hosted flow that returns payment instructions (e.g. a QR code) directly; other methods - bank transfer, card, Boleto, PicPay, PagoEfectivo, aggregated wallets, cash, mobile money, PSE, Nequi, Transfiya, BRE-B, Efecty, SPEI, CoDi - redirect the customer to a SmartFastPay-hosted page. Available methods/currencies depend on what's enabled for your account.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7e8f9a01-2b3c-4d5e-8f67-8a9b0c1d2e3f",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8f9a0b12-3c4d-4e6f-8a78-9b0c1d2e3f4a",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+5511999999999"
      }
    }
  }
}

Important

  • customer.name is forwarded as a single string (not split into first/last).
  • country is derived automatically from the selected service/currency, not from customer.address.
  • For Pix, Pix QR, and Nequi (with the nequi_new_format option enabled) specifically, customer.phone and a dynamic customer document (e.g., CPF) are additionally required - the Dashboard/API shows the exact field for your service.
  • For bank transfer in Mexico specifically, customer.phone is also required (falls back to the phone Constant if missing).

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

  • nequi_new_format -> optional, boolean - switches Nequi to the newer hosted flow (same one used by Pix/Pix QR), which requires customer.phone and a customer document; when disabled, Nequi uses the older flow instead.

Constants (fallback fields)

  • phone -> fallback for customer.phone, used only for bank transfer payments in Mexico.

Refunds

This connector does not support refunds.

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

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, bank transfer, BRE-B, or Transfiya, depending on what's enabled for your account. Required fields vary by method - the Dashboard shows the exact field list once a method is selected.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "9a0b1c23-4d5e-4f7a-8b89-0c1d2e3f4a5b",
      "service": "pix_brl",
      "currency": "BRL",
      "amount": 10,
      "fields": {
        "pix_key": "11999999999",
        "type": "CPF",
        "number": "12345678900"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0b1c2d34-5e6f-4a8b-8c90-1d2e3f4a5b6c",
      "service": "pix_brl",
      "currency": "BRL",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com"
      },
      "fields": {
        "pix_key": "11999999999",
        "type": "CPF",
        "number": "12345678900"
      }
    }
  }
}

Important

Required fields depend on the payout method:

  • Pix -> fields.pix_key (forwarded as the transfer destination), plus the recipient's document type/number.
  • Bank transfer -> fields.bank_code, fields.bank_account_number, fields.bank_account_type.
  • Transfiya -> fields.phone_number (forwarded as the transfer destination, without the + prefix).
  • BRE-B -> fields.destination_key (forwarded as the transfer destination).

The recipient's phone is taken from a method-specific field (e.g. phone_number/beneficiary_phone) if present, otherwise from customer.phone, otherwise from the phone Constant.

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. Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in SmartFastPay's own back-office.
  2. Active reconciliation is available - both Payments and Payouts support an active status request, in addition to the asynchronous callback.
  3. No refunds - this connector does not support refunds through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Client ID/Client Secret for the selected environment
  • Payment fails with a missing document error -> for Pix, Pix QR, and the new Nequi flow, make sure the customer's document field for the selected service is provided
  • Refund request fails -> refunds aren't supported by this connector
  • Currency or service is not supported -> confirm allowed methods/currencies in your SmartFastPay account and in Corefy

Question

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