Transaction Flow

Initial transaction

1. On the merchant's website, the consumer selects Skrill as their preferred payment method.
2. The merchant/PSP requests a session identifier (SID) by passing the consumer and transaction details (e.g. amount, currency, and language) and the 1-Tap parameters to the Skrill Quick Checkout.
3. Skrill returns the generated SID.
4. The consumer is redirected to the Skrill Quick Checkout. The session identifier is included in the redirect URL.
5. Skrill displays the payment page.
6. The consumer pays using the preferred payment method and confirms the transaction.
7. Skrill requests payment authorization from the consumer’s bank, third-party provider, or card issuer.
8. The bank/provider approves or rejects the transaction.
9. Skrill displays the confirmation page, containing the transaction result, on the Skrill Quick Checkout.
10. Skrill sends an asynchronous notification, sent to the merchant/PSP status URL or IPN (instant payment notification), confirming the transaction details and status.
11. These details include the rec_payment_id of the 1-Tap payment, which can be used for future 1-Tap debits from the consumer’s account.

Subsequent payments

1. On the merchant's checkout page, the consumer selects Skrill 1-Tap.
2. The merchant checks the status of the 1-Tap mandate using their records or the Merchant Query Interface (MQI).
3. If the consumer is already set up for 1-Tap, the merchant makes the prepare request.
4. Both frn_trn_id and rec_payment_id should be provided.
5. The Skrill 1-Tap Payment Interface returns the session identifier (SID).
6. The merchant/PSP sends the execution request with the returned SID.
7. The Skrill 1-Tap Payment Interface validates the request.
8. Skrill requests payment authorization from the consumer’s bank, third-party provider, or card issuer (if required).
9. The bank/provider approves or rejects the transaction.
10. The Skrill 1-Tap Payment Interface sends a response with the transaction status.
11. The transaction status notification is also posted to the merchant’s status URL.
12. The merchant notifies the customer of the status of the 1-Tap payment.

Integration

Specific input parameters for the TRANSACTION call

For standard input parameters, see Input parameters for the TRANSACTION call.

Specific output parameters for the TRANSACTION call

This payment method will emit the SPECOUT.SRCEMAIL output parameter, which contains the email address that was used by the consumer.

For standard output parameters, see Output parameters for the TRANSACTION call.

TRANSACTION call input

tag=skrill
&txtype=TRANSACTION
&countrycode=DE
&currency=EUR
&amount=1055
&merchanttxid=AsvMktWtw8Mg
&login=johndoe
&password=wasdHF67gSAaa
&contractid=johndoe
&channel=testchannel
&merchantredirecturl=https%3A%2F%2Fmerchant.com%2Fwork%2Fppro2%2Flanding.php
&notificationurl=https%3A%2F%2Fmerchant.com%2Fwork%2Fppro2%2Fnotification.php
&specin.dynamicdescriptor=DynDescriptor
&accountholdername=John%20Doe
&specin.email=test%40gmx.de
&specin.consumerid=XYZ321
&specin.onetapmaxamount=600
&specin.onetapnote=Tap%20Note
&returnmode=urlencodeext

TRANSACTION call output

REQUESTSTATUS=SUCCEEDED
&STATUS=SUCCEEDED
&TXID=950179543
&ERRMSG=
&CHANNEL=testchannel
&TAG=skrill
&PAYMENTGUARANTEE=NONE
&REDIRECTSECRET=rKR1fb4aAxwLN6fVOf0yXAQ6CRD1cew2
&[email protected]

Annotations

• An initial 1-Tap payment is performed if:
  • You specify a 1-tap maximum amount
  • The transaction's amount exceeds a previously-specified maximum amount
• Consumers will be redirected to a Skrill login form before making the actual payment. Otherwise, the login form is not displayed.
• Specify the 1-Tap maximum amount in the currency’s smallest representable unit (e.g. cents).