Field mapping
| Field | Meaning | How to choose it |
|---|---|---|
title | Customer-facing title. | Required. |
description | Customer-facing description. | Optional. |
amount | Amount to collect. | Optional; omit for flexible-amount links. |
currency | Fiat or crypto asset to collect. | Use a supported asset reference, for example naira or usdt. |
type | Payment link rail. | Use fiat for bank-transfer style links or crypto for crypto links. |
network | Crypto network. | Required for crypto links; use a network reference for the selected currency. |
expiresIn | Link lifetime in hours. | Positive number. |
metadata | Partner-defined reconciliation data. | Optional object. Store your own IDs such as customerId, ticketId, eventId, liveTagId, vendorId, or partnerReference. |
id | Payment link ID. | Returned by create/list endpoints; use it to expire a link. |
code | Public link code. | Returned by create/list endpoints; use it with /public/payment-links/{code}. |
Allowed values
| Field | Allowed values |
|---|---|
type | crypto, fiat |
status | pending, completed, expired, failed, cancelled |
Endpoints
Create a payment link
Idempotency-Key when creating or expiring payment links. The response includes the link code and payment details. Store the returned ID and code for support and reconciliation.
Use metadata for your own business mapping. Rivo stores it and returns it with the payment link, but Rivo does not enforce partner-specific meaning for those fields.
Example response:
creationStatus may initially be pending while the provider generates the deposit address. Continue reading the payment link or use the public link endpoint until the address details are available.