Testing and go-live
Build and test your integration in Sandbox first. Sandbox transactions don't move real money and don't settle on the card networks.
Setting up Sandbox
Open Fabric sets up the following for you:
- Expense Management enabled on your Sandbox account, with your market and a default brand.
- The
exp.bankscope available to your Sandbox API client. An admin on your Open Fabric portal account adds it to the client. - Your core ledger API registered: your Sandbox base URL and the credential Expense Management uses to call it.
- The first admin console user, invited as a console admin. They can invite the rest of your staff. See Admin console and roles.
You then onboard a test business in the admin console, linked to a test funding account in your Sandbox core ledger. Its admin issues a virtual card to a test employee.
Test scenarios
Card payments
- A payment within policy: the check answers
approve, and you posthold+authorized, thendebit+clearedafter clearing. The employee sees the payment in the app. - A payment in a blocked category: the check answers
decline. You decline and postdeclinedwithdecline.source: expense_mgmt. The employee sees the reason and can ask for approval. - After an approved exception, the same payment is approved.
- A payment over your card limits is declined and can't be appealed.
- An incremental authorization sends a check with
stage: incrementaland postshold_change. - A reversal before clearing posts
hold_release+reversed. - A refund after clearing posts
credit+refunded. - A check that times out: your stand-in applies, and the payment still shows in the app after you post its events.
- A card or account that Expense Management doesn't manage gets
not_applicable.
Account events
- A repeated
event_idreturnsduplicate. - Events delivered out of order still end in the right status.
- A malformed event in a batch is
rejected, and the rest of the batch applies. - Fees and transfers on the funding account appear in the business's account activity.
Core ledger APIs
- Linking a funding account in the admin console finds the account and shows the masked number and holder name.
- A QR payment from the app is submitted, debited, and completes through an account event.
- A reimbursement run sends payouts that reach
settledthrough account events. - A repeated payout
referencedoesn't pay twice. -
404is returned only for payments you never received.
Operations
- Your brand is published and shows on the dashboard, the app and the invite emails. See Branding.
- A business admin accepts the invite, sets up the workspace and invites an employee. See How businesses get started.
- Your support staff can resend invites and freeze a card.
Going live
- Share your test results with your Open Fabric contact.
- Set up production: Open Fabric enables Expense Management on your production account. You add the
exp.bankscope to your production API client and share your production core ledger API base URL and credential. - Publish your brand in the production admin console.
- Set your card limits if you use them.
- Onboard a pilot business and run a first live payment end to end.
- Open to more businesses.
Support
Your staff provide first-line support to your business customers. Open Fabric provides second-line support to your staff. Reach us at api@openfabric.co.