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.Simulate failed payment link payments in Sandbox
You can now force a payment link payment to fail in Sandbox. Create a link for a trigger amount, such as14.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.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}/dataand uploads files withPOST /v1/information-requests/{informationRequestId}/documents. It describes requirements, entries, andcardinality. - Displaying account information reads accounts from
GET /v1/accounts, and explains automatic sweeps withtagsandrelatedTransactionId.
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.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_REVIEWWITHDRAWAL_ACCOUNT_NOT_SUPPORTEDPROCESSING_FAILEDOUTCOME_UNDER_INVESTIGATIONREVERSAL_IN_PROGRESSWITHDRAWAL_SYSTEM_ERRORDEPOSIT_SYSTEM_ERRORAUTOSWEEP_SYSTEM_ERROR
INTERNAL_ERRORnow covers only system errors on transactions other than withdrawals, deposits, and auto-sweeps. Most failures previously reported asINTERNAL_ERRORnow use one of the new codes.RISK_REJECTIONnow covers only automated risk declines. A decline after a review reportsDECLINED_AFTER_REVIEW, and a risk system error reports the system error code for the transaction type.BANK_REJECTIONnow includes direct debit returns. A failure to debit funds reportsPROCESSING_FAILEDinstead.
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.New guide for taking a payment link payment
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.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.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: anhttpsURL the buyer returns to after paying. It requirespaymentLinkId.
?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.New 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 withX-Meridian-Resource-Type: payment_link_transaction:payment_link_transaction_createdpayment_link_transaction_status_updatedpayment_link_transaction_succeededpayment_link_transaction_failed
Generic transaction events removed for payment links
Payment link transactions no longer send the generictransaction_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.