FAQs

Q: Is there a specific order for when we receive the `card_activation_ready` webhook and when we receive the `iframe_ready` webhook?

No specific order, the order is non-deterministic because we have two background jobs running for these two webhooks.

Q: How do I simulate a transaction in sandbox environment?

Please set up a session with us where we will go through a suite of test cases of varying transaction type. Also, keep the test card ready with sufficient balance and share the opaque_id with the representative.

Q: For reversal and refund cases, how do I link it with the original deduction transaction?

You can use retrieval_reference_number (RRN) or transaction_id to find the original transaction.

Q: What is the expected time delay between remote host authorization and webhook notification requests?

The expected time delay between authorization and webhook should be within seconds. Transaction webhook usually comes in a few seconds after you approve

Q: What is the timeout threshold for the RHA endpoint, and what happens if a timeout occurs?

The current timeout threshold is 6 seconds. If your endpoint does not respond within this window, the transaction will be automatically declined. Please note that StraitsX does not perform automatic retries for RHA timeout events.

Q: How do we verify First-Party OCT Transactions?

To ensure the transaction is first-party, we will compare the Customer Name registered in our system against the Sender Name provided in the transaction details. Our name matching algorithm is designed to be flexible and will safely ignore the following discrepancies:

Whitespaces: "John Doe" matches " John Doe "
Case-sensitivity: "John Doe" matches "JOHN DOE"
Name Order: "John Doe" matches "DOE JOHN"

However, the following are examples of what will not match and will result in a rejected transaction:

Missing components: "John Doe" will not match "John"
Different names: "John Doe" will not match "Jane Doe"
Typos or Abbreviations: "John Doe" will not match "Jon Doe" or "J. Doe"