Get EFT Session Details
GEFT
Session Details
GET
Get EFT Session Details
Retrieve comprehensive session information including verified payor account details.
To successfully call this endpoint, you must have a valid access token from the /Authorize endpoint.
Get Session Details
Use this endpoint to retrieve full, verified payor account information along with all session-level details required for payment validation.Availability of Account Details
Important: Payor account details become available only after the session has passed the “Initiated” stage. Before that point, the payor account section will be returned empty. This endpoint provides:- Complete session information: All details from session creation
- Verified account details: Bank account information after user authentication
- Payment validation data: Information needed for transaction processing
- Identity verification results: User identity matching status
Request Example
Response Structure
The response includes comprehensive session information and, once available, detailed payor account verification data:Response Fields
Session Information
- sessionId: Unique session identifier
- status: Current session status
- step: Current step of the session flow, an object with
current,aggregationRequestId, andpadId. Possiblecurrentvalues:Start: session opened; user has entered the flowConsent: Flinks consent screen (whenshowConsentScreenis enabled)BankSelection: user is choosing their financial institutionBankConnection: user is logging into / connecting their bankAccountSelection: user is selecting which account to useAmountSelection: user is entering the amount (skipped whenamountis preset)GuaranteeOffer: guarantee offer presented to the userReview: user reviews the payment detailsPad: user reviews and signs the PAD agreementComplete: flow finished
- referenceId: Your internal reference ID
- amount: Payment amount (null if not yet set)
- type: Payment type (always “EFT” for GEFT)
- direction: Payment direction (always “DEBIT” for GEFT)
- currency: Payment currency (always “CAD”)
Options
- guarantee.enable: Whether a guarantee was requested
- notificationPreferences.language: Language preference (“EN” or “FR”)
- showConsentScreen: Whether Flinks consent screen is displayed
- limits: Minimum and maximum allowed payment amounts
- amountModification: Whether the user can modify the amount
- redirectPreferences: Redirect mode and URLs for session completion
Payor Information
- Personal details: Name (firstName, lastName, middleName), email as provided during session creation
- Verified account: Bank account information obtained after user authentication (institutionCode, transitNumber, accountNumber, accountLabel, availableBalance)
- Address: Street address, city, province, country, postal code
Payee Information
- Account details: Destination account information (institutionCode, transitNumber, accountNumber, accountLabel)
Guarantee Details
- guaranteeOffered: Whether a guarantee was offered
- guaranteeAccepted: Whether the guarantee was accepted (null if not yet decided)
- highestDebitAmountToGuarantee: Maximum debit amount eligible for guarantee
- Risk levels: overallRiskLevel, transactionRiskLevel, userRiskLevel, otherRiskLevel (Unknown, Low, Medium, High)
- guaranteedEftType: Type of guarantee coverage (Full, Partial, Minimal)
User Details
- matchingPerformed: Whether identity matching was performed
- nameMatch: Name matching score (0 to 100)
Data Availability Timeline
Before User Authentication (Status: Initiated)
After User Authentication (Status: Completed/Failed)
Use Cases
Payment Validation
- Verify user identity matches bank account holder
- Confirm account details for reconciliation
- Validate guarantee status before processing
Audit and Compliance
- Complete transaction trail for regulatory requirements
- Identity verification documentation
- Account verification records
Customer Support
- Comprehensive session information for issue resolution
- Account details for payment troubleshooting
- Complete payment history and status
Reconciliation
- Match payments to internal records using referenceId
- Account details for settlement verification
- Complete payment lifecycle information
Error Responses
Session Not Found
Authentication Required
Insufficient Permissions
Security Considerations
Data Protection
- Account numbers: Masked for security (showing only last 4 digits)
- Personal information: Handle according to privacy regulations
- Access controls: Ensure proper authentication and authorization
Compliance
- Data retention: Follow regulatory requirements for payment data
- Audit trails: Maintain complete records for compliance
- Privacy: Protect customer personal and financial information
Best Practices
When to Call This Endpoint
- After status changes: When polling shows status updates
- For reconciliation: During end-of-day processing
- For support: When investigating payment issues
- For compliance: When audit trails are required
Data Handling
- Cache appropriately: Avoid excessive API calls
- Secure storage: Protect sensitive account information
- Access logging: Log all access to session details
Status Values
Thestatus field reflects the session’s progress. Retrieve this endpoint until the session reaches a terminal state (Completed, Failed, Canceled, or Expired).
Related Endpoints
- Create Session - Initialize GEFT payment session
- Cancel Session - Terminate active session
Authorizations
Bearer token obtained from the /api/v1/authorize endpoint.
Headers
Bearer token received from the /authorize endpoint.
Pattern:
^Bearer .+Path Parameters
The session identifier returned when the session was created.
Response
Session details retrieved successfully
Example:
"850750a4-3021-4061-ac03-a8d873aa4179"
Current session status.
Available options:
Initiated, Failed, Cancelled, Expired, Completed Example:
"USER12345"
Example:
100
Available options:
EFT Example:
"EFT"
Available options:
DEBIT Example:
"DEBIT"
Available options:
CAD Example:
"CAD"
Always null for EFT. Funds settle to your configured account.
Example:
"2026-06-04T14:30:00Z"