The Provider Sequence Management feature allows you to define the order in which Paystrator routes transactions across multiple connected providers. This ensures high reliability, failover handling, and flexible routing per product or destination (e.g., bank, eWallet, or virtual account).
How It Works
Each Paystrator product (e.g., Send Money, Receive Money – Virtual Account, eWallet, QR Code) can have its own routing sequence. When a transaction is initiated:
- Paystrator attempts the first provider in the list.
- If it fails (e.g., provider timeout, maintenance, or rejection), the system automatically tries the next provider.
- The sequence continues until the transaction succeeds or all providers are exhausted.
You can configure these sequences** per destination** (e.g., specific VA Bank or eWallet), giving you fine-grained control over routing.
Viewing Provider Sequence
To access this page:
Dashboard → Providers → Sequence Management
You’ll see tabs for each product:
- Send Money
- Receive Money
- QR Code
- Virtual Account
- eWallet
For each tab, Paystrator shows a list of configured sequences.
Fields Displayed
| Field | Description |
|---|---|
| Destination | Bank, VA Bank, eWallet, or QR Code type |
| Provider Sequence | Ordered list of active providers |
| Last Updated On | Timestamp of the last modification |
| Updated By | User who last changed the configuration |
Default Sequence
When you add providers, Paystrator automatically creates a Default Sequence for each product. Here are some rules you might want to know about sequences in Paystrator.
- New providers are auto-appended to the end of the default sequence.
- Default sequences apply to all destinations unless a Custom Sequence is defined.
- Providers in Maintenance mode still appear but are skipped during routing.
- For QR Code, the default sequence always uses QRIS as the only option.
Adding a Custom Sequence
You can define custom sequences for specific destinations such as a particular VA Bank or eWallet.
- Click Add Custom Sequence.
- Choose your destination (e.g., BNI, DANA, OVO).
- Drag and drop providers into your preferred order.
- Toggle providers on/off to include or exclude them.
- Click Save when finished.
Custom Sequence Example
| Destination | Sequence |
|---|---|
| Default (VA) | Provider 1 → Provider 2 → Bank A → Bank B → Provider 3 |
| Custom (BCA Open VA) | Bank A → Provider 2 → Provider 3 |
Explanation:
When a transaction targets BCA VA, Paystrator will use the custom sequence; otherwise, the default sequence applies.
Rotating Sequence (Advanced)
Rotating sequences allow you to load balance traffic across multiple custom configurations.
Rotating Sequence Example
Below is a rotating sequence example, let's say for sending money to a bank.
| Sequence | Sequence |
|---|---|
| Seq 1 | Provider 1 → Provider 2 → Bank A |
| Seq 2 | Provider 2 → Provider 1 → Bank A |
Explanation:
Routing alternates between them per transaction: Seq 1 → Seq 2 → Seq 1 → Seq 2
You can also assign weights to favor one sequence more often (e.g., Seq 1 used twice as often as Seq 2 by adding Seq 3 that contain the same sequence as Seq 1).
Maximum 10 custom sequences per destination are supported.
Notes & Best Practices
- Always verify that each provider in your sequence is active and properly credentialed.
- Use custom sequences for critical destinations (e.g., top VA banks) to ensure redundancy.
- Review logs regularly to confirm updates or detect configuration drift.
- Sandbox and Production sequences are managed separately, updates in one do not affect the other.