Merchant Portal Guide

This guide covers the day-to-day use of the Foundry Pay 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.

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 one is reversed)
• A refund fails to process
• A card authorization expires and needs a new card from the buyer to complete the payment
• 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. Four 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 Foundry 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. Amounts here are already net of Foundry's own fees (those are deducted before your balance is calculated, not shown as a line item against your own payouts).

• 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).
• The deposits table shows Gross / Fees / Net for each deposit, not just one final number — Gross is your sales before chargebacks/refunds for that deposit, Fees 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 amount range, to find a specific deposit or transaction quickly.
• Export either "Payouts only" (one row per deposit) or "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 Total Deductions 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.

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.

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 Foundry-hosted form on that link. Payment requests expire after 60 minutes.

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.

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. Send the resulting link to the buyer the same way as the original Card Entry URL; once they submit a new card, it's linked to this payment request automatically — no other changes needed before re-authorizing.

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.

Status Tabs

Authorization Extension & Reauthorization

If a payment sits in Authorized or Partially Captured for too long without being (fully) captured, its authorization can expire on the card network. Foundry watches for this automatically:

• It proactively tries to extend the authorization's hold before it expires.
• If that isn't possible, it transparently re-authorizes the remaining balance against the same saved payment method — you don't need to do anything, and the payment stays in whatever status it was in.
• Only if both of those fail does the payment move to Expired. A payment that already had a partial capture stays Partially Captured in that case — the money already captured is unaffected, only the remaining un-captured balance can no longer be collected.

Open a transaction's detail drawer and check the Authorization section to see this history — each extension or reauthorization attempt, its outcome, and (for a successful reauthorization) the PSP reference change.

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.

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

Refund history appears as indented rows below the transaction, showing amount, status, reason, and date.

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
• Timeline — timestamps for each status change
• Network Reference — the payment network reference number (useful for disputes)
• Capture history — each capture with amount, shipment reference (if set), status, and timestamp
• Refund history — each refund with its status and network 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.
• 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).
• 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) and an optional Shipment Reference to tag the capture to a specific shipment.

• CSV format: referenceId,amount,shipmentReference (amount and shipment reference are 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.

API Activity (/api-activity)

For self-diagnosing your own integration. Every call your integration made to Foundry's API using your API key, and what Foundry sent back — no need to file a support ticket to find out why a call failed or what Foundry 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.
• 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.

Team

Invite colleagues to access the portal. Invited users receive a Cognito invitation email.

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.

Webhook

Configure the URL where Foundry Pay sends payment event notifications.

1. Enter your webhook URL (must be publicly reachable)
2. Click Save & regenerate secret
3. Copy the signing secret immediately — it is shown only once

Use the signing secret to verify that incoming webhook requests are genuine. See the Partner Integration Guide for signature verification code examples.

Webhook Deliveries

Shows recent webhook delivery attempts. Use this to verify that your endpoint is receiving events and to inspect the exact payload that was sent.

Filter by status: All · Delivered · Failed · Pending

Click any row to expand and view the full JSON payload that was sent. Failed deliveries are retried automatically — if an endpoint is consistently failing, check that the URL is correct and publicly reachable.

Team Activity (/team-activity)

For knowing who did what, and when. A record of the actions your team has taken in the portal — captures, voids, refunds, and team member invites/removals — 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 Foundry 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.