Sessions Scenarios
- Session Mode:
PAYMENT_WITH_WALLET| API Scope:user| API Endpoint:v2/sessions| Interaction mode:UI - Maximum number of payment methods: 2
- Payment Type:
SALE - Transaction Type: Any
- Mode:
One Time PayPay & Save - Payment Type:
PRE-AUTH
Business Use Caseโ
Standard Payment Scenariosโ
Standard Payment Scenarios
| ID | Scenario | Retry Attempt Pending | User Type | First Payment Status | Second Payment Status | Amount | CCG Actions | Final Session Status | Payment Status |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Both Payments Successful | N/A | Customer/Agent | โ COMPLETED | โ COMPLETED | Split (e.g. 60ยข + 40ยข) | Process both payments | โ COMPLETED | SUCCESS |
| 2 | Allow Single Payment | N/A | Customer/Agent | โ COMPLETED | N/A | Full (e.g. 10ยข) | Capture the Transaction | โ COMPLETED | SUCCESS |
| 3 | One Payment Success, Another Payment โ FAILED | Yes | Customer/Agent | โ COMPLETED | โ FAILED | Split (e.g. 60ยข + 10ยข) | Reverse first payment | โณ INITIATED | โ FAILED |
| 4 | Amount less than 1 cent for one payment | Yes | Customer/Agent | โ FAILED | โ FAILED | Invalid (e.g. 0.5ยข + 9999.5ยข) | Fail transaction, show error | โณ INITIATED | โ FAILED |
3DS Authentication Scenariosโ
3DS Authentication Scenarios
| ID | Scenario | Retry Attempt Pending | User Type | First Payment Status | Second Payment Status | Amount | Final Session Status | CCG Actions |
|---|---|---|---|---|---|---|---|---|
| 5 | Card 1 requires 3DS auth (not COMPLETED) | Yes | Customer | 3DS Required | โ AUTHORIZED | Split (e.g. 60ยข + 40ยข) | โ FAILED | 3DS Auth unsuccessful for one card, another card transaction should be cancelled |
| 6 | Card 1 requires 3DS auth (Agent Session) | Yes | Agent | 3DS Required | โ COMPLETED | Split (e.g. 60ยข + 40ยข) | โ FAILED | 3DS Auth not allowed for agent, CCG cancels auth of card2 |
| 7 | Card 1 requires 3DS auth (โ COMPLETED successfully) | N/A | Customer | โ COMPLETED | โ COMPLETED | Split (e.g. 60ยข + 40ยข) | โ AUTHORIZED | 3DS Auth โ COMPLETED and CCG captures both card |
ACH Specific Scenariosโ
ACH Specific Scenarios
| ID | Scenario | Retry Attempt Pending | User Type | First Payment Status | Second Payment Status | Amount | CCG Actions | Final Session Status | Payment Status |
|---|---|---|---|---|---|---|---|---|---|
| 8 | Consent Unavailable | Yes | Any | โ FAILED (ACH) | NA | Split (e.g. 60ยข + 40ยข) | Consent is required for ACH | INITIATED | โ FAILED |
Retry Exhausted Scenarioโ
When all retry attempts for a split tender transaction are exhausted, no further retries are allowed for that session. The user must initiate a new transaction if they wish to try again. This ensures transaction integrity and prevents indefinite retry loops.
Retry Exhausted
| ID | Scenario | Retry Attempt Pending | User Type | First Payment Status | Second Payment Status | Amount | CCG Actions | Final Session Status | Payment Status |
|---|---|---|---|---|---|---|---|---|---|
| 9 | Retry Exhausted | โ No | Any | โ FAILED | โ COMPLETED | Split (e.g. 60ยข + 40ยข) | No Retry Attempts Left | โ FAILED | โ FAILED |
Special Cases: Guest Fallback and Abandoned Payment Scenariosโ
These scenarios cover edge cases where the session is abandoned or a guest fallback is triggered. Each scenario ensures that incomplete or abandoned payments are handled gracefully, maintaining system integrity and user experience.
Special Cases: Guest Fallback and Abandoned Payment Scenarios
Abandoned Payment Scenariosโ
If a session is abandoned (e.g., browser closed or session timeout), any pending or partially completed payments are automatically cancelled to prevent orphaned transactions and ensure customer funds are not held.
| ID | Scenario | Retry Attempt Pending | User Type | First Payment Status | Second Payment Status | Amount | CCG Actions | Final Session Status | Payment Status |
|---|---|---|---|---|---|---|---|---|---|
| 10 | Browser Closure Before handling 3ds challenge of second payment | Yes | Customer | โ COMPLETED | Pending | Split (e.g. 60ยข + 40ยข) | Cancel dangling transaction when session is cancelled | ๐ซ CANCELED | โ FAILED |
| 11 | Session TimeOut | Yes | Customer | โ COMPLETED | Pending | Split (e.g. 60ยข + 40ยข) | Cancel dangling transaction when session is expired | ๐ EXPIRED | โ FAILED |
Guest Fallbackโ
If a split tender attempt fails, guests may be offered a fallback to complete the transaction with a single payment method, improving the likelihood of successful checkout.
| ID | Scenario | Retry Attempt Pending | User Type | First Payment Status | Second Payment Status | Amount | CCG Actions | Final Session Status | Payment Status |
|---|---|---|---|---|---|---|---|---|---|
| 12 | Guest Payment FallBack | Yes | Guest | โ COMPLETED | N/A | Full (e.g. 60ยข) | One Time Pay with one Payment Method | โ COMPLETED | N/A |