
Rampnow
The crypto infrastructure for future. Buy and sell stable coins with ease and security on our user-friendly platform.
Supports in this guide: Payments
Provider website: rampnow.io
What you need to do for start processing transactions (brief summary)
- Get your credentials (from Rampnow)
- Connect in Dashboard
- Send an API request
Prerequisites: get from Rampnow
Send a connection request at rampnow.io or contact your Rampnow account manager directly to get your account verified and receive the following credentials.
- Email -> Corefy field
email. - Client ID -> Corefy field
client_id. - Client secret -> Corefy field
client_secret.
Payments processing (connect Provider account, create payment-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open Rampnow in the provider directory and press Connect at Rampnow Provider Overview page in the New connection section.
Step 2 - Fill in fields and select settings
- Client ID
- Client secret
- Test Mode -> (enable if you are using sandbox credentials)
Success
You have connected Rampnow Provider account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice and redirects the customer to Rampnow's hosted checkout. Card, Apple Pay, Google Pay, BLIK, Bancontact, iDEAL, and Sofort are all supported on this same connection, selected automatically per service.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "65e53d1e-1b6e-491c-a221-e6ba9b17f916",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 1,
"customer": {
"reference_id": "444",
"name": "Rajesh Madhaiyan",
"email": "test@example.com",
"address": {
"full_address": "Test address",
"country": "FR",
"city": "Paris",
"street": "Test address"
}
}
}
}
}
Important
customer.name, customer.email, and customer.address (at least country) are all required - the request fails if any are missing. There are no Constants for this connector, so none of these can be filled in from account-level fallback values.
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "65e53d1e-1b6e-491c-a221-e6ba9b17f916",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 1,
"customer": {
"reference_id": "444",
"name": "Rajesh Madhaiyan",
"email": "test@example.com",
"phone": "+442012341234",
"address": {
"full_address": "Test address",
"country": "FR",
"region": "Paris",
"city": "Paris",
"street": "Test address"
}
}
}
}
}
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
Refunds
Rampnow does not support refunds.
Additional info
- No active reconciliation - Rampnow statuses arrive only via the asynchronous callback; there is no active status request available for this connector.
- No recurring - this connector does not support saving/charging a token through Corefy.
- No Options or Constants are configured for this connector.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the Email, Client ID and Client secret for the selected environment (
test_mode) - Payment fails for missing customer data ->
customer.name,customer.email, andcustomer.address.countryare required for every payment - Payment stuck pending with no status update -> this connector has no active status request; confirm your callback endpoint is reachable and correctly configured
- Refund fails -> Rampnow does not support refunds through Corefy
Question
Still looking for help connecting your Rampnow account? Please contact our support team!