-
Notifications
You must be signed in to change notification settings - Fork 2
Payments
To create a linkID payment session, you have to piggyback a LinkIDPaymentContext on the LinkIDAuthenticationContext or the LinkIDLTQRContent .
The flow is the same as a linkID authentication session with the exception that you'll receive an asynchronous payment poke whenever the payment has been completed ( or failed ).
When polling linkID, you'll have to monitor the value of the LinkIDPaymentState property in the LinkIDAuthPollResponse for the state of the payment.
The amount to be payed. The currency can be traditional ( e.g. EUR) in which case the amount is specified in cents ( 100 == 1 EUR ) or in wallet coin type ( see Wallets )
An optional description regarding the content of what is being payed for. Will be displayed in the client, as in the payment confirmation e-mail and the linkID user's activity feed.
For each linkID application, multiple payment profiles can be configured, e.g. for certain payments only creditcards are allowed, for others creditcards and SEPA is allowed, ... . You can override the default payment profile with this property.
Time linkID will wait for receiving an ok from a PSP asynchronously for the state of the payment. Defaults to 5 seconds. After that the LinkIDPaymentState will be WAITING_FOR_UPDATE.
Whether a payment mandate should be created when this linkID payment session finishes successful. You can provide a mandate description and an optional reference for this. If no reference is specified, linkID will generate one for you.
If the mandate is created, the application can make further payments without user interaction via the linkID mandatePayment API call.
Allow partial payments, this flag does not make sense if you allow normal payment methods.
Only allow linkID wallets for this payment.
When a PSP has an update for a certain payment order, you can get a notification via the LinkIDNoticicationTopic urn:net:lin-k:linkid:topic:payment:update
Have a look here for more info