Rixsus

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to Rixsus's hosted checkout. Rapipago, Pagofacil, and bank transfer (ARS) and PSE (COP) are all supported on this same connection.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "03e7bbc6-61f3-48c8-91ce-1cd3af97564c",
      "service": "bank_transfer_ars_hpp",
      "currency": "ARS",
      "amount": 100,
      "customer": {
        "reference_id": "4e527231-5f45-4874-bd99-24d7d221129f",
        "name": "John Wick",
        "email": "john@example.com"
      },
      "service_fields": {
        "document_id": "33123123"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "e3aa279e-1809-4089-affd-b5e8dcc4a4e9",
      "service": "bank_transfer_ars_hpp",
      "currency": "ARS",
      "amount": 100,
      "customer": {
        "reference_id": "8da3c1db-9d5f-45f3-aa52-ee8375045eaf",
        "name": "John Wick",
        "email": "john@example.com",
        "phone": "+5491123456789",
        "address": {
          "full_address": "Main street 123"
        },
        "metadata": {
          "ip": "127.0.0.1"
        }
      },
      "service_fields": {
        "document_id": "33123123"
      }
    }
  }
}

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. Available separately per service (rapipago_ars_hpp, pagofacil_ars_hpp, bank_transfer_ars_hpp, pse_cop_hpp).

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)

• FIRST_NAME -> customer.name (first part)
• LAST_NAME -> customer.name (second part)
• EMAIL -> customer.email
• PHONE -> customer.phone
• ADDRESS -> customer.address.full_address
• IP -> customer.metadata.ip

Refunds

Rixsus does not support refunds.

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 to a bank account.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "39efd2f3-032f-4e85-895a-4608a2907cd9",
      "service": "bank_transfer_ars",
      "currency": "ARS",
      "amount": 10,
      "fields": {
        "account_type": "CBU",
        "beneficiary_name": "John",
        "beneficiary_lastname": "Wick",
        "bank_account": "test",
        "beneficiary_address": "Main street 123",
        "beneficiary_document_id": "71640610",
        "beneficiary_email": "john@example.com",
        "beneficiary_phone": "+5491123456789"
      }
    }
  }
}

Payout - MAX

Payouts don't use customer - all recipient details are passed under fields, as shown above. There is no separate MAX variant.

Refunds

Rixsus does not support refunds for Payouts.