Documentation Index
Fetch the complete documentation index at: https://docs.trymaven.com/llms.txt
Use this file to discover all available pages before exploring further.
Connecting Fiserv
Maven connects to Fiserv (Commerce Hub / Payments Live) using your API Key and API Secret. These credentials let Maven create charges or vault cards on your behalf.Prerequisites
- A Fiserv developer account
- API Key and API Secret
- A Maven app
Getting Your Credentials
Register at portal.fiserv.dev
Go to portal.fiserv.dev and complete registration. Verify your email and set up MFA.
Navigate to API Keys
Once logged in, go to the API Keys page. A pre-generated Test Sandbox Key is already there with access to all APIs and a dummy Store ID — no approval step needed for sandbox.
Connecting in Maven
Go to Payments
In the Maven Dashboard, open your app and click the Payments tab.
Enter Credentials
- Environment: Sandbox or Production
- API Key: Your Fiserv Api-Key
- API Secret: Your Fiserv API Secret
- Production Base URL (optional, production only): Override if Fiserv assigned your tenant a non-default hostname. Leave blank to use the standard hostname.
Sending the form to your customer
If your customer is the merchant (i.e., the Fiserv account is theirs, not yours), click Copy link next to Save. That generates a single-use, 7-day link they can open in a browser and paste their credentials directly into a hosted form. Their keys are written to your project without you ever seeing them.Sandbox Testing
The portal.fiserv.dev sandbox key works immediately on signup — no approval. Use it withmvn_test_ API keys to test without real charges.
A useful sandbox test card:
| Field | Value |
|---|---|
| Number | 4035 8740 0042 4977 |
| Expiry | Any future date |
| CVV | 977 |
Processor Response Fields
Charge Mode
| Field | Description |
|---|---|
fiserv_transaction_id | Fiserv ipgTransactionId |
fiserv_order_id | Fiserv orderId |
fiserv_payment_token | Reusable payment token (returned on every charge — store it for future re-charges) |
fiserv_state | CAPTURED (auto) or AUTHORIZED (manual) |
fiserv_status | APPROVED on success |
approval_code | Fiserv authorization code |
response_code | Processor response code (00 = success) |
response_message | Processor response message |
card_brand | Card brand (e.g. VISA) |
card_last4 | Last 4 digits |
Tokenize Mode (Vault)
| Field | Description |
|---|---|
fiserv_payment_token | Reusable Fiserv payment token (UUID) |
card_brand | Card brand |
card_last4 | Last 4 digits |
ipg_transaction_id | Fiserv ipgTransactionId from the tokenization request |
Using Tokenized Cards
After tokenizing, charge the stored FiservpaymentToken directly. Each request is HMAC-SHA256 signed:
