PayNearMe

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

Choose Currency and Features. You can set these according to what's available on your PayNearMe account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice. PayNearMe requires customer name, phone, and a billing address by default - there's no placeholder fallback for this flow, so send real values.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 15,
      "customer": {
        "reference_id": "cus_123",
        "first_name": "John",
        "surname": "Smith",
        "phone": "1111111111",
        "address": {
          "full_address": "10 Downing Street",
          "post_code": "12345"
        }
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 15,
      "customer": {
        "reference_id": "cus_123",
        "first_name": "John",
        "surname": "Smith",
        "email": "johnsmith@gmail.com",
        "phone": "1111111111",
        "address": {
          "full_address": "10 Downing Street",
          "country": "US",
          "region": "NY",
          "city": "New York",
          "street": "10 Downing Street",
          "post_code": "12345"
        }
      }
    }
  }
}

This flow is a genuine H2H integration - card data is submitted directly to PayNearMe (no redirect), in two steps handled automatically by Corefy: an order is created first, then the card is submitted and charged. Note this connector expects customer.first_name/customer.surname separately rather than a combined customer.name.

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)

This connector has no Dashboard-configurable Constants for the H2H Merchant account - customer name, phone, and address must be provided in the request itself.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Site identifier
• Secret key
• Test Mode -> (enable if you are using sandbox credentials)
• Currency / Features -> choose the methods enabled on your PayNearMe account (Card, Google Pay, Apple Pay, Cash, ACH)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to PayNearMe's hosted payment page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "ach_usd_hpp",
      "currency": "USD",
      "amount": 15
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "ach_usd_hpp",
      "currency": "USD",
      "amount": 15,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "1111111111"
      }
    }
  }
}

This Provider account flow is a redirect (hosted payment page): Corefy creates the order server-side, then redirects the customer to PayNearMe's page to complete the payment. It covers several methods with a single account - besides ACH (ach_usd_hpp shown above), it also supports card, Google Pay, Apple Pay, and Cash deposit; the exact service codes available for your account are configured in the Dashboard connection form (Currency / Features) rather than being a fixed list, so check there or with your account manager for the codes to use for methods other than ACH.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (2)

• finalize_after_minutes - finalizes a still-pending payment automatically after the given number of minutes.
• save_ach_payment_method_after_deposit (ACH only) - keeps the customer's ACH payment method on file after a successful deposit for future reuse.

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)

• FIRST_NAME -> customer.first_name
• LAST_NAME -> customer.surname
• YEAR_OF_BIRTH -> derived from customer.date_of_birth
• EMAIL -> customer.email
• PHONE -> customer.phone
• STREET -> customer.address.street
• CITY -> customer.address.city
• STATE -> customer.address.region
• POST_CODE -> customer.address.post_code

These constants are configured per service code (e.g. separately for ach_usd_hpp), not globally for the account.

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.

Payout - MIN (ACH)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "ach_usd",
      "currency": "USD",
      "amount": 15,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "account_number": "8453846359",
        "routing_number": "021606742",
        "account_type": "checking"
      }
    }
  }
}

Payout - MAX (ACH)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "ach_usd",
      "currency": "USD",
      "amount": 15,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "4444444444",
        "date_of_birth": "1990-01-01",
        "address": {
          "full_address": "242 Greene St",
          "country": "US",
          "region": "NY",
          "city": "New York",
          "street": "242 Greene St",
          "post_code": "01965"
        }
      },
      "fields": {
        "account_number": "8453846359",
        "routing_number": "021606742",
        "account_type": "checking"
      }
    }
  }
}

This connector also supports card-token payouts (use payment_card_usd, with fields.token set to a previously-issued PayNearMe payment-method token instead of fields.account_number/routing_number/account_type) for customers who already have a card on file with PayNearMe. For a new ACH recipient, PayNearMe creates the payment method from fields.account_number/routing_number/account_type plus the customer's name/address on the fly; if the customer already has a saved PayNearMe ACH method (from a prior deposit - see save_ach_payment_method_after_deposit above), Corefy reuses it automatically instead of resending bank details.

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

Currently available options (1)

• finalize_on_success_status - finalizes a payout as soon as PayNearMe reports a successful status, instead of waiting out the full return window.

Constants (fallback fields)

This connector has no Dashboard-configurable Constants for payouts - customer.name and the ACH fields are always taken from the request (or from a previously-saved PayNearMe payment method).