PayPlanet

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

Choose Currency and Features. USD and UZS are confirmed; check with your Corefy account manager which are enabled for your account.

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request.

Payment - MIN

POST /api/payment-invoices

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

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}

customer is optional - only customer.reference_id is actually forwarded (as the buyer's remote ID), everything else about the customer is skipped on this flow. CVV is required for USD; for UZS specifically, CVV is optional - a placeholder is used internally if you don't collect it.

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.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

Choose Currency / Features - this connector focuses on Latin American local payment methods - see Additional info for the full list.

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to the chosen local method's payment page.

Payment - MIN

POST /api/payment-invoices

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

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "pse_cop_hpp",
      "currency": "COP",
      "amount": 50000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "phone": "+15551234567",
        "address": {
          "street": "1 Main street"
        }
      },
      "fields": {
        "document_type": "CC",
        "document_number": "1234567890"
      }
    }
  }
}

customer is optional on every local method, but which fields each one actually forwards differs - see Additional info for the breakdown. fields.document_type/fields.document_number (Colombian ID type/number) apply where relevant.

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.

Connect Provider account in Corefy Dashboard

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

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card or a local bank/instant-payment account.

Payout - MIN (card)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_usd",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

fields.card_number is required. This connector also supports card payouts in KZT (use payment_card_kzt) - for KZT specifically, customer.reference_id is also used, and the card's expiry/holder come from the stored card data, not from fields.

Payout - MIN (Colombian bank transfer)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "bank_transfer_cop",
      "currency": "COP",
      "amount": 50000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      },
      "fields": {
        "document_type": "CC",
        "document_number": "1234567890",
        "account_number": "1234567890",
        "bank_code": "001",
        "bank_name": "Bancolombia",
        "bank_account_type": "savings"
      }
    }
  }
}

The exact required subset of fields.* varies by destination method - see Additional info for the field list per country.

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.