Card (Rillpay)
ID: card-rillpay | Provider: Rillpay | Region: International
Overview
Card payments routed through the Rillpay gateway. The customer is redirected to a Rillpay-hosted checkout form to enter their card details. Sweuze never receives or stores PAN data.
paymentMethod Fields
| Field | Required | Description |
|---|---|---|
id |
yes | Must be card-rillpay |
customerType |
yes | Customer segmentation used by Rillpay. One of new, new_affiliate, existing. |
kycStatus |
yes | Current KYC status. One of verified, unverified. When verified, Rillpay skips its own KYC step. |
customerType Values
| Value | Meaning |
|---|---|
new |
First-time depositor |
new_affiliate |
First-time depositor acquired through an affiliate channel |
existing |
Returning customer that has previously transacted |
Conditional Customer Requirements
When paymentMethod.id is card-rillpay, the following customer fields are required in addition to customer.id:
emailphone(E.164 format)firstNamelastNamedateOfBirth(ISOYYYY-MM-DD)
Omitting any of these returns a 422 validation error.
Request Example
{
"paymentMethod": {
"id": "card-rillpay",
"customerType": "new",
"kycStatus": "verified"
},
"reference": "ORDER-12345",
"customer": {
"id": "cust_abc123",
"email": "customer@example.com",
"phone": "+441234567890",
"firstName": "John",
"lastName": "Doe",
"dateOfBirth": "1990-01-15",
"ip": "192.168.1.1"
},
"amount": "150.00",
"currency": "EUR",
"returnLinks": {
"default": "https://yourproduct.com/return",
"cancel": "https://yourproduct.com/cancel"
}
}
Response Action
Rillpay always returns a redirect action. Redirect the customer to action.url (a Rillpay-hosted checkout page pre-loaded with an encrypted gdata payload).
{
"type": "redirect",
"method": "GET",
"url": "https://checkout.rillpay.com/cc-form?gdata=...&m=...",
"expiresAt": "2025-11-18T14:45:00.000+00:00"
}
The redirect URL is short-lived (typically a few minutes). If the customer does not reach Rillpay before expiresAt, create a new intent.
Status Flow
requires_action- redirect the customer toaction.url.processing- Rillpay is authorizing/capturing the card.succeeded- payment captured. Fulfill the order.failed- card declined, 3DS failed, or provider error.canceled- the customer abandoned the flow or the redirect expired.
Webhook Events
Rillpay card payments emit the full set of payment intent events (payment_intent.initiated, payment_intent.requires_action, payment_intent.processing, payment_intent.succeeded, payment_intent.failed, payment_intent.canceled) and the associated payment.* events once a payment is created.