
Intersect
Intersect enables you to process payments in any way that works for your business, whether it's through your website, mobile app, or manual transactions.
Supports in this guide: Payments
Provider website: intersectbanking.com
What you need to do for start processing transactions (brief summary)
- Get your credentials (from Intersect)
- Connect in Dashboard
- Send an API request
Prerequisites: get from Intersect
Contact your Intersect account manager to get your account verified and receive the following credentials.
- API key -> Corefy field
api_key. - API secret -> Corefy field
api_secret.
Payments processing (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Intersect in the provider directory and press Connect at Intersect Provider Overview page in the New connection section.
Step 2 - Fill in fields and select settings
- API key
- API secret
- Currency / Features -> choose values available for your account
Success
You have connected Intersect H2H Merchant account!
First request to Corefy API (MAX)
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 - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "5b38f2c4-bb54-4f21-923c-ca3e00e00a00",
"service": "payment_card_usd_hpp",
"currency": "USD",
"amount": 10,
"customer": {
"reference_id": "cus_123",
"name": "John Snow",
"email": "johnsnow@example.com",
"phone": "+15551234567",
"address": {
"country": "US",
"city": "New York",
"region": "NY",
"street": "1 Main street",
"post_code": "10001"
}
}
}
}
}
Important
customer.name, customer.email, customer.phone, and the full customer.address (country, region, city, street, post_code) are all strictly required - Intersect's own validation rejects the request before it's even sent if any of these are missing from the request and not covered by a Constant. There is no MIN example for this reason; every field shown above is effectively mandatory.
Constants (fallback fields)
Constants are static values that Corefy can send to Intersect 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 -> the request fails validation before reaching Intersect
Currently available constants (constant -> Corefy API field)
FIRST_NAME->customer.name(first part)LAST_NAME->customer.name(last part)EMAIL->customer.emailPHONE->customer.phoneCARDHOLDER_NAME-> falls back for the card's embossed name if the card data itself doesn't supply oneSTREET->customer.address.streetCOUNTRY->customer.address.countryREGION->customer.address.regionCITY->customer.address.cityPOST_CODE->customer.address.post_code
Refunds
Intersect does not support refunds.
Additional info
- Active reconciliation is available - both the asynchronous callback and an active status request can finalize the payment.
- No recurring - this connector does not support saving/charging a token through Corefy.
- No hardcoded placeholder fallback values are used - if a required field is missing from both the request and the Constants, the request is rejected rather than filled in with fake data.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the API key and API secret
- Payment rejected for missing customer/address fields -> set Constants to cover any fields you don't send per request, or include them directly
- Refund fails -> Intersect does not support refunds through Corefy
Question
Still looking for help connecting your Intersect account? Please contact our support team!