Skip to main content

← All Payment Providers

​
Overview

Nekuda provides virtual card issuance for payments. When you submit a Nekuda payment method, Rye creates a mandate with Nekuda, reveals virtual card details, and processes payment directly with the merchant. This is a partner integration — no card data is handled by your application.

​
Usage

Pass the Nekuda payment method to the Rye API using the nekuda_token type and the user’s unique Nekuda identifier.

​
Single-Step Purchase

curl -X POST https://api.rye.com/v1/checkout-intents/purchase \
  -H "Authorization: Bearer $RYE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "productUrl": "https://example-store.myshopify.com/products/example-product",
    "quantity": 1,
    "buyer": {
      "firstName": "Jane",
      "lastName": "Doe",
      "email": "jane@example.com",
      "phone": "+15551234567",
      "address1": "123 Main St",
      "city": "New York",
      "province": "NY",
      "postalCode": "10001",
      "country": "US"
    },
    "paymentMethod": {
      "type": "nekuda_token",
      "nekudaUserId": "<NEKUDA_USER_ID>"
    }
  }'

​
Two-Step Flow (Add Payment to Existing Intent)

curl -X POST https://api.rye.com/v1/checkout-intents/{id}/payment \
  -H "Authorization: Bearer $RYE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentMethod": {
      "type": "nekuda_token",
      "nekudaUserId": "<NEKUDA_USER_ID>",
      "nekudaMandateData": {
        "key": "value"
      }
    }
  }'

​
Notes

  • The Nekuda integration requires partner onboarding. Contact dev@rye.com for access.
  • nekudaMandateData is optional. Use it to pass additional context (as key-value pairs) during mandate creation.
  • nekudaUserId is a unique user identifier provided by Nekuda.