Merchant Portal Guide

This guide covers the day-to-day use of the VersaTrade Payments merchant portal for collecting payments, managing transactions, and configuring your account.

Accessing the Portal

Navigate to portal.pay.emun1.com and sign in with the credentials from your invitation email. If you haven't received an invitation, contact support@markettime.com.

Search

The Search box at the top of the sidebar finds a payment request, payment or customer from whatever you have to hand: an order, PO or invoice number, a buyer's email or company, a card's last four digits, an amount (540, $1,234.56), a PSP reference, or an ID. Results appear as you type, grouped by kind. Use the arrow keys and Enter, or click one, to open it. Press ⌘K (Mac) or Ctrl+K from any page to jump to the box. It searches only your own account.

Notifications

A bell icon at the top of the sidebar shows a badge when you have unread notifications — click it to see recent activity without having to go looking for it. You'll be notified when:

• You receive a chargeback or an ACH return (or one is reversed)
• A refund fails to process
• A card authorization is due for capture (day 3), is voided automatically (day 5), or expires — see Capture Reminders and Automatic Voids
• A payout to your bank fails or is returned
• A fee can't be collected from your balance
• A debit from your bank account fails or is returned by your bank
• A buyer's bank sends corrected bank account details for an ACH payment
• Your account finishes verification and is ready to accept payments
• Your webhook endpoint appears to be failing repeatedly

Click a notification to mark it read, or Mark all read to clear the badge. New activity appears automatically — no need to refresh the page.

Dashboard

The Dashboard is your default landing page. It shows a summary of recent payment activity and embedded reporting components for deeper financial data.

Stats

Select a time period — Last 7 days, Last 14 days, or Last 30 days — using the buttons at the top right. The tiles update to show:

A daily volume chart and payment method mix (Cards / ACH / Wallets) appear below the tiles.

Account Status

A checklist shows the health of your account setup:

If any item shows a warning, go to Settings → Verification Status for details.

Reporting Components

Below the stats, four panels provide detailed financial data:

• Transactions Overview — filter and review individual transaction records
• Disputes Overview — manage open disputes and respond to chargeback requests
• Reports Overview — download settlement and financial reports
• Payouts Overview — review completed payouts for reconciliation

These panels have their own internal date filters and are updated in real time.

Payouts (/payouts)

For reconciling your bank deposits. Every deposit VersaTrade Payments has paid into your bank account, and the sales, refunds, and chargebacks that added up to it — the report your accounting team needs to tie a bank statement line back to specific orders. Sales are already net of VersaTrade Payments' fee on each sale. Fees charged separately (monthly, chargeback, refund and the like) are collected from your balance and appear as a Fee line in the deposit they came out of, and a bank top-up appears as a Top-up line, so every deposit adds up to its lines.

• The top tiles show Deposits (total paid to your bank + number of deposits), Chargebacks and Refunds (broken out separately, not lumped into one deduction figure), and Net Payout (what actually reached your bank, with the total transaction count for the period).
• Recent Payout Activity shows the real-time status of each payout as it moves to your bank — separate from the deposit history below it, which comes from the periodic payout report.
• The deposits table shows Gross / Deductions / Net for each deposit, not just one final number — Gross is your sales before chargebacks/refunds for that deposit, Deductions is what was deducted, Net is what actually hit your bank.
• Click any row in the deposits table to expand it and see every transaction, refund, and chargeback that composed that specific deposit, with the customer name, order/invoice reference, and Adyen PSP reference for each.
• Search by order/invoice reference or PSP reference, or filter by date and amount range, to find a specific deposit or transaction quickly.
• Export either Export payouts (one row per deposit) or Export payouts + details (one row per transaction within each deposit) as CSV for your own records.
• A chargeback or refund can land in a different deposit period than the original sale — if Chargebacks/Refunds and the change in Deposits don't tie out exactly for a given period, that's normal timing, not a data error.

Payment Requests

Payment requests represent a buyer session where a card or bank account is collected. A payment request must be Collected before you can authorize funds.

Viewing Payment Requests (/payment-requests)

Use the status tabs to filter by All, Pending, Collected, or Expired.

Your filters, search and page stay in the address bar, here and on Customers and Payouts, so reloading keeps your view and you can bookmark it or send the link to a colleague.

The search bar filters by reference ID, company name, or buyer email address. Results update as you type. Narrow further with From/To date filters and Min amount/Max amount — all filters combine, and a Clear filters link appears once any of them is set.

Click Export CSV to download the current filtered list. An export covers at most a year: with no dates set it covers the last year, and a longer From/To range is refused, so export longer periods in parts.

Creating a Single Payment Request

Click + New Payment and fill in the form:

After creating, copy the Card Entry URL from the payment request detail page and send it to the buyer. The buyer enters their card in the VersaTrade Payments hosted form on that link. Payment requests expire after 60 minutes, unless you send the payment link from the detail page, which keeps it open 7 days.

Uploading Multiple Payment Requests (CSV)

Click Upload CSV to create many payment requests at once.

CSV columns (download the template for the exact format):

After uploading, a preview shows the rows that will be created. Click Create N Payments → to submit. A live counter tracks progress. When complete, export the results CSV to get the iframeUrl for each payment request — send these URLs to your buyers.

Payment Request Detail

Click any row in the list to open the detail page. Key sections:

Card Entry URL — the link to send to the buyer. Available to copy while status is Pending.

Send Payment Link (visible while status is Pending) — click Send Payment Link to email the buyer a link to a hosted payment page showing the order's line items and amount (if set), where they can enter or select a payment method — VersaTrade Payments' equivalent of a Stripe Payment Link. It's the same Card Entry URL under the hood, just delivered by email instead of you sending it yourself. You can send it more than once if the buyer says they didn't get it. Sending it keeps the request open 7 days from then (instead of 60 minutes), and while it's unpaid the buyer gets a reminder 3 days after you send it and another the day before it closes. Once sent, the details show Link sent (with any reminders since) and Buyer opened: when the buyer first opened the payment page, or "Not yet".

Additional Charges (visible once a card is collected, manual capture mode only) — add line-item charges on top of the original amount before authorizing. For example, add a shipping charge after the original order amount was set.

Authorize Payment — click Authorize $X.XX to submit the payment to the card network. On success, you are taken to the resulting transaction record. See Capture Modes for when this step is needed.

Update Card (visible once a card is collected) — click Generate Card Update Link to create a fresh card entry link for this buyer, e.g. if their stored card expired, was declined, or otherwise needs to be replaced. Click Email to buyer to send it: the email asks them to update their card for this order, charges nothing, and keeps the link open 7 days. Or copy the link and send it yourself, within the hour it otherwise lasts. The link asks for a new card and doesn't offer the buyer's saved ones. Once they submit it, it's linked to this payment request automatically — no other changes needed before re-authorizing.

Level 2/3 data (card requests with order details) — whether the order details your platform sent qualify for lower card interchange: Qualifies for Level 3, Qualifies for Level 2 only, or Does not qualify, with what's missing for Level 3 and any values that won't count because they're malformed. It applies when a commercial card is captured in full; the payment works either way. To improve it, ask your platform to send the missing fields.

Capture Modes

Auth-only / Manual Capture (default)

The buyer's card is stored with a zero-dollar authorization. No money moves until you explicitly click Authorize in the portal (or call the API). Use this for order workflows where you review, adjust, or fulfill before charging.

Immediate Capture

Authorization and capture happen when the buyer submits the payment form. Money moves immediately — no portal action required. Use this for invoices or flows where you want funds settled at the point of collection.

ACH

ACH follows the same capture modes as card. With immediate capture, the bank debit occurs at the time of entry and no further action is needed. With manual capture (the default), the bank account is tokenized only — you'll see an Authorize button on the payment request, then a Capture button once authorized, same as a manual-capture card payment. Either way, bank settlement takes 1–3 business days after the debit is initiated.

Transactions

The Transactions page shows all payments that have been authorized or captured. Search by reference ID or company, and narrow further with From/To date filters and Min amount/ Max amount (filtered on the authorized amount) — all filters combine, with a Clear filters link once any of them is set. Click Export CSV to download the current filtered list (at most a year; with no dates set, the last year).

Status Tabs

(Partially Captured payments are under the Partial tab.)

Capture Reminders and Automatic Voids

A card authorization holds the buyer's funds only until you capture it. VersaTrade Payments does not extend or re-authorize a card authorization, so capture promptly:

• Day 3: if a card payment is still Authorized or Partially Captured, you get a notification (and an account alert email, if those are on) reminding you to capture it, with the date it will be voided.
• Day 5: whatever is still uncaptured is voided automatically, and you're notified. Anything already captured stands. To charge the buyer after that, authorize the order again.
• If the card network expires the authorization first, a payment with nothing captured moves to Expired; one with a partial capture stays Partially Captured and only the uncaptured remainder is lost.

This applies to card payments only, not ACH. Open a transaction's detail drawer and check the Authorization section to see these events — the reminder, the automatic void, and their outcomes.

Capturing a Payment

On an Authorized or Partially Captured transaction, click Capture to open the capture dialog:

1. The remaining balance is pre-filled as the capture amount — edit it down to capture only the amount for the current shipment.
2. Optionally enter a Shipment Reference (e.g. SHIP-001) to tag this capture to a specific shipment for reconciliation.
3. Any prior captures for this payment are listed in the dialog so you can see what has already been settled.
4. Click Capture to confirm.

If the captured amount is less than the full authorized balance, the transaction moves to Partially Captured and the remaining balance stays open for future captures. Once the full authorized amount is captured, the status becomes Captured.

ACH payments can only be captured in full — the capture amount is fixed at the remaining balance, because a second capture isn't possible on an ACH payment.

Voiding a Payment

On an Authorized or Partially Captured transaction, click Void to cancel the remaining uncaptured balance. A confirmation dialog appears before the void is processed. Any amounts already captured before the void are not reversed.

Issuing a Refund

On a Captured, Partially Captured, or partially refunded transaction, click Refund to expand the refund form inline:

1. Enter the refund amount (defaults to the full refundable balance; partial amounts allowed)
2. Select a reason: Requested by customer · Issue with item sold · Fraudulent · Duplicate · Other
3. Click Issue Refund

The full refund amount comes out of your balance; VersaTrade Payments' fee on the original payment is not returned.

Refund history appears as indented rows below the transaction, showing amount, status, reason, and date. A refund that failed shows the reason it was refused.

Transaction Detail

Click any transaction row to open the detail drawer on the right side. It shows:

• Amounts — Authorized, Captured, Remaining (shown when Partially Captured), Refunded, and Net
• Payment method — card brand and last 4 digits (or bank, for ACH)
• Chargeback / ACH return — the reason code and reason, when a payment has been disputed or its bank debit returned
• Timeline — when the payment was created, authorized, and captured
• Adyen PSP reference — the payment's processor reference, with a Copy button (useful for disputes and support requests)
• Capture history — each capture with amount, shipment reference (if set), status, and timestamp. For a card capture it also says whether its Level 2/3 data qualified for lower interchange: qualified, downgraded or refused by Adyen (with Adyen's reason), data missing, or not sent because the capture was partial
• Authorization — capture reminders, automatic voids, and other authorization events
• Refund history — each refund with its reason, status, and PSP reference

Customers (/customers)

Your buyers' payment history and saved cards in one place — no more piecing it together by searching through individual transactions.

• The list shows each buyer's email, company, number of payments, total captured, and their most recent payment — search by email or company to find someone quickly. Searching by an email the buyer used before also finds them, listed under their current one.
• Click a customer to see their full payment history with you and any cards they've saved for reuse (brand, last 4 digits, expiration, and when they consented to save it). A card the buyer has removed no longer appears.
• This only ever shows your own history with a buyer — if the same buyer has also purchased from another business on the platform, none of that shows up here.

Batch Operations

Batch operations let you authorize or capture multiple payments in one action — the primary workflow for processing a batch of invoices.

Batch Authorize

1. Go to Batch Operations → Batch Authorize
2. Add rows manually (Reference ID + optional override Amount), paste CSV, or import a CSV file
3. CSV format: referenceId,amount (one per line; amount is optional)
4. Click Run Batch Authorize →
5. Review the results: succeeded (green ✓) and failed (red ×) items are listed with details
6. Click Export Results CSV to download a report

A warning appears if you add more than 100 items. Very large batches may take longer to process.

Batch Capture

Same workflow as Batch Authorize, using the Batch Capture tab. Each row can include an optional Amount (to capture less than the full remaining balance). To tag a capture with a shipment reference, capture it individually from Transactions.

• CSV format: referenceId,amount (amount is optional)
• If amount is omitted, the full remaining balance is captured
• A payment with a partial capture moves to Partially Captured; include it in a subsequent batch to capture the next shipment

API Keys (/api-keys)

API keys allow your platform (or a partner integration) to create payment requests programmatically without using the portal.

Creating an API Key

1. Enter a descriptive label (e.g. EMUN1 production)
2. Click Create
3. Copy the key immediately — it is shown only once and cannot be retrieved again

Revoking an API Key

Click Revoke next to any key and confirm. Revoked keys stop working immediately. Create a new key before revoking an old one if you need uninterrupted API access.

Webhook Endpoints (/webhook-endpoints)

Configure where VersaTrade Payments sends payment event notifications. You can add multiple endpoints — every one receives every event type, so you can, for example, point one at production and another at a monitoring or staging system without them interfering with each other.

Adding a Webhook Endpoint

1. Enter the URL (must be publicly reachable) and an optional label to tell endpoints apart
2. Click Add Endpoint
3. Copy the signing secret immediately — it is shown only once and applies to that endpoint alone

Use each endpoint's own signing secret to verify that incoming webhook requests to it are genuine. See the Partner Integration Guide for signature verification code examples.

Revoking a Webhook Endpoint

Click Revoke next to any endpoint and confirm. Revoked endpoints stop receiving events immediately — your other endpoints are unaffected.

Webhook Deliveries

Click Load Deliveries to see recent webhook delivery attempts across all your endpoints. Use this to verify that a given endpoint is receiving events and to inspect the exact payload that was sent.

Filter by status (All · Delivered · Failed · Pending) or by a specific endpoint.

Click any row to expand and view the full JSON payload that was sent. Failed deliveries are retried automatically for up to 3 days after the event, with growing waits; under a failed one's status you'll see when it's next tried, or Gave up after 3 days. Resend sends any delivery's event to its endpoint again right away, as a new delivery with its own retries (the original stays in the list as it was). If one endpoint is consistently failing, check that its URL is correct and publicly reachable; your other endpoints keep working independently.

API Activity (/api-activity)

For self-diagnosing your own integration. Every call your integration made to the VersaTrade Payments API using your API key, and what we sent back — no need to file a support ticket to find out why a call failed or what we actually returned.

• Only shows calls made with an API key — actions taken by your team through the portal appear in Team Activity instead, not here.
• The Source column shows which key made each call — your own API key's label, or, if you're linked to a software platform (e.g. MarketTime, EMUN1) using a partner-scoped key on your behalf, that platform's name alongside its key label. Entries from before this tracking existed show —.
• Filter by HTTP method or result (success/error), or search by path.
• Click any row to expand it and see the full request and response bodies side by side.

Settings

Business Profile

Update your business name, phone, and mailing address. Email cannot be changed from the portal — contact support to change your account email.

Branding

Set a display name, accent color, logo, and support contact info for your business — used to brand buyer-facing emails and the hosted payment page (see Send Payment Link).

• Display Name — falls back to your business name if left blank.
• Accent Color — a hex color (e.g. #1A73E8).
• Logo — PNG or JPEG, up to 2 MB. Click Upload (or Change to replace an existing logo, Remove to clear it).
• Support Email / Support Phone — optional contact info shown on these emails.

Buyer Notifications

Choose which emails VersaTrade Payments sends to your buyers on your behalf, branded with the settings above.

• Send buyers an email receipt when a payment is collected — off by default. Turn this on only if you don't already send your own payment confirmation; a buyer whose card is charged through VersaTrade Payments will otherwise receive this receipt automatically once it's enabled.
• Send buyers an email when a refund is issued — off by default, same reasoning as the receipt email above.
• Send buyers an email if a payment attempt fails — off by default. Useful for deferred captures (manual-capture payments captured later), where the buyer isn't present to see the failure happen the way they would during checkout.
• Send buyers a reminder email when their card on file is expiring soon — off by default. The email has an Add a new card link, open for 7 days, so the buyer can enter the replacement from it. Checked periodically; a buyer gets at most one reminder per card, regardless of how many checks run while that card is still in its expiring window.
• Remind buyers about payment links they haven't paid — on by default, since it only follows a payment link you chose to send. Two reminders at most per send: 3 days after it, and the day before the link closes.

Account Alerts

Separate from Buyer Notifications above — this is VersaTrade Payments emailing you about activity on your own account.

• Email me about account activity — on by default. Covers the same events as the notification bell: chargebacks, failed refunds, capture reminders and voided or expired authorizations, failed payouts, uncollected fees, failed bank debits, corrected ACH details, account verification, and a webhook endpoint that's repeatedly failing. Some of these have real deadlines (e.g. responding to a chargeback), so this is on unless you turn it off. A chargeback alert says the date it must be responded to by, and 3 days before that date you're reminded if it still hasn't been answered. That reminder is sent even with this setting off, since a missed deadline loses the dispute. The dashboard's Needs attention list shows the next deadline too. Respond from Disputes on the dashboard.
• Send account emails to — where these alerts go, and also where fee change notices and bank debit notices go (those two are always sent). Leave it blank to use your account's business email.

Team

Click Load Team to see who has access, then invite colleagues by email. Invited users receive an invitation email.

You can invite a colleague as a Member, an Admin, or View only. Admins manage the account: the team, API keys, webhook endpoints and settings. Members do everything else (payment requests, captures, refunds, payouts, customers) and can see the account pages but not change them. View only is for a finance person or an outside bookkeeper: they see payments, payment requests, customers, payouts, reports and settings, and can't change anything. Their portal leaves out the action buttons and the Batch Operations, API Keys and Webhook Endpoints pages, the dashboard has no Disputes panel for them, and any change they try is refused.

To remove a user, click Remove next to their row and confirm.

See Team Activity below for a record of what each team member has actually done.

Verification Status

Shows your current verification state. If any capability shows an error, expand it to see the specific issue and the required remediation steps. Click Refresh Status after completing any requested steps.

If your account is not yet fully verified, the Complete Onboarding section appears with a Launch Onboarding button that takes you to the onboarding wizard.

Bank Account

Click Manage Bank Account to add or update the bank account that receives payouts from your balance account. This opens a secure bank account form directly in the portal.

ACH Company ID

The ID our payment processor makes ACH debits under. Banks that block or filter ACH debits return them unless this ID is allowed, so share it with buyers who pay you by bank account, and give it to your own bank too.

Team Activity (/team-activity)

For knowing who did what, and when. A record of the actions your team has taken in the portal — authorizations, captures, voids, refunds, batch runs, payment requests created, charges added or amounts amended, card update links, team member invites/removals, and API keys and webhook endpoints created or revoked — so you always know who was responsible for a given change without having to ask around.

• Only actions taken through the portal appear here. Payments captured, refunded, or created through your own API integration are not shown — those already have their own visibility in Transactions and Payment Requests, and there's no specific team member behind that traffic to attribute it to.
• Filter by date range, action type, or search by the person's email or the action's detail text (e.g. an order reference or an invited email address).
• If VersaTrade Payments support performs an action on your behalf (with your permission, to help resolve an issue), it appears here too, labeled accordingly.

Support

Contact support@markettime.com with your reference ID for any payment-specific inquiries.