Skip to main content
Meridian Accounts for BusinessGuides
End-to-end walkthrough for Meridian Accounts

New end-to-end walkthrough

The Meridian Accounts for Business docs now include an End-to-end walkthrough. It follows one customer through the full flow in Sandbox: create a user, enroll, read the account, simulate a USD deposit, register a bank account, and pay out in PHP.Making a payout also gains a USD bank account example and an ACH payout example.
Realtime CollectionsGuides
Simulate failed payments in Sandbox
You can now force a payment link payment to fail in Sandbox. Create a link for a trigger amount, such as 14.14 for a failed bank debit, and pay it as the buyer. Simulating failed payments lists each trigger amount and every webhook it sends.This works in Sandbox only. It does not affect production.
Meridian Accounts for BusinessGuides
Onboarding and account guides match the current API

Onboarding and account guides updated

Two guides described earlier versions of the API. They now match the API reference. The API itself has not changed.
  • Onboarding your customer saves values with POST /v1/information-requests/{informationRequestId}/data and uploads files with POST /v1/information-requests/{informationRequestId}/documents. It describes requirements, entries, and cardinality.
  • Displaying account information reads accounts from GET /v1/accounts, and explains automatic sweeps with tags and relatedTransactionId.
Meridian Accounts for BusinessGuides
Design reviews before going live

Design reviews added to Go live

Go live has a new first step. Share your UX designs with your Solutions Engineer once your project kicks off. Meridian’s UX, risk, and legal reviews must be complete before it issues production credentials.The guides also show the enrollment field and deposit instruction labels the API returns, so your screens can use them as they are.
Retail U.S. AccountsMeridian Accounts for BusinessWebhooks
More specific transaction failure codes

More specific transaction failure codes

Meridian now reports transaction failures with more specific codes, so you can tell your customer what happened and whether to retry. No code is removed.

Retail U.S. Accounts

statusReason on virtual account transactions, in the API and the Virtual Account Transaction webhook, has eight new codes:
  • DECLINED_AFTER_REVIEW
  • WITHDRAWAL_ACCOUNT_NOT_SUPPORTED
  • PROCESSING_FAILED
  • OUTCOME_UNDER_INVESTIGATION
  • REVERSAL_IN_PROGRESS
  • WITHDRAWAL_SYSTEM_ERROR
  • DEPOSIT_SYSTEM_ERROR
  • AUTOSWEEP_SYSTEM_ERROR
Three existing codes change scope:
  • INTERNAL_ERROR now covers only system errors on transactions other than withdrawals, deposits, and auto-sweeps. Most failures previously reported as INTERNAL_ERROR now use one of the new codes.
  • RISK_REJECTION now covers only automated risk declines. A decline after a review reports DECLINED_AFTER_REVIEW, and a risk system error reports the system error code for the transaction type.
  • BANK_REJECTION now includes direct debit returns. A failure to debit funds reports PROCESSING_FAILED instead.
See Failure reasons for what each code means and what to do.

Meridian Accounts for Business

reason on transactions, in the API and the Transaction webhook, has four new codes. Each replaces a broader code for one case:A decline after a review still reports RISK_PROVIDER_REJECTED. See Reason codes for what each code means.
Never retry a transaction that failed with OUTCOME_UNDER_INVESTIGATION (Retail U.S. Accounts) or CREDIT_OUTCOME_UNKNOWN (Meridian Accounts for Business). The money may already have moved, so a retry can pay twice.
Realtime CollectionsGuides
Payment link and buyer session guide
The Realtime Collections docs now include Collect a payment. It walks through creating a link with one session, then creating a second session when you want the buyer to return to your site after paying. It also explains why the buyer session can pay only one link and expires after 15 minutes.
Meridian Accounts for BusinessGuides
Go live guide

New guide for going live

The Meridian Accounts for Business docs now include a Go live page. It covers the Sandbox checks to complete and how to request production access through the Help Center. It also lists what to include in your request and what Meridian does before issuing your production credentials.
Realtime Collections
Redirect buyers after a payment link payment

Send buyers back to your site after they pay

Create a Session accepts two new optional fields:
  • paymentLinkId: the payment link the buyer pays with this session.
  • redirectUrl: an https URL the buyer returns to after paying. It requires paymentLinkId.
Send the buyer to the payment link URL with ?sessionKey=<sessionKey> appended. The buyer must pay within the 15-minute session window. A session created with a paymentLinkId cannot create payment links. Sessions created without these fields work as before.
Realtime CollectionsWebhooks
Payment link transaction webhooks
Meridian now sends a webhook every time a payment link transaction changes status. Each webhook carries both the payment link and the transaction.New events, all with X-Meridian-Resource-Type: payment_link_transaction:
  • payment_link_transaction_created
  • payment_link_transaction_status_updated
  • payment_link_transaction_succeeded
  • payment_link_transaction_failed
Register an endpoint for each event you want to receive.Payment link transactions no longer send the generic transaction_created, transaction_succeeded, and transaction_failed events. They send the payment_link_transaction_* events instead. Meridian used to report REVERSAL_IN_PROGRESS as a failure. It now sends a payment_link_transaction_status_updated event instead. The transaction_* events are unchanged for Meridian Accounts.Learn more in Tracking a payment link payment with webhooks and the Payment Link Transaction reference.