Features overview

Use the Features API to list features, check a customer's eligibility, and activate the card feature, virtual_cards. Activation creates the customer's card application.

How it works

You switch features on per customer. These routes serve cards only. The catalog lists six features, but the one you activate here is virtual_cards. Open accounts, wallets and payouts with their own APIs. The lifecycle has three steps:

1. Discover. Call GET /v1/risk/features. Without a customer_id, it returns the feature catalog. With a customer_id, it also shows which features are activated for that customer.
2. Check eligibility. Call POST /v1/risk/features/eligibility to see the customer's outstanding requirements. For virtual_cards, eligible stays false until activation, because you send provider_data at activation. Pending items have no provider field.
3. Activate. Call POST /v1/risk/features/activate with the feature_id and the required provider_data. Always send your business's card account as provider_data.account_id. After a liveness check, send a new Idempotency-Key. See Activate feature.

Endpoints

Authentication

All requests use https://api.gravv.xyz/v1/ and authenticate with the Api-Key header. See Authentication for details.