Common errors with the Copy and Pay integration

Follow

This page describes the most common errors that can come up when doing a Copy and Pay integration.

Invalid or missing parameter 200.300.404

You try to GET the payment status in step 3, but you get an error message invalid or missing parameter.

{"result":{"code":"200.300.404","description":"invalid or missing parameter - (opp) No payment session found for the requested id - are you mixing test/live servers or have you paid more than 30min ago?"},"buildNumber":"82d393aad4390f43d567cfe15346f9e89bda7fae@2018-05-25 08:09:59 +0000","timestamp":"2018-05-28 07:36:55+0000","ndc":"5a17f05d53944ae1b2fe3d22f03e0881"}

Possible fixes

  • You are mixing up live end test endpoints
  • You have waited more than 30 minutes with step 3 and therefore the checkout id has expired
  • You are requesting the status with the checkout ID AND the parameters (username, password, entityId). If this is the case, remove the parameters form the request and use the checkout id only. For example https://test.oppwa.com/v1/checkouts/xxx5E5B054.sbg-vm-tx02/payment
  • You are requesting the payment status for the second time. You can only request the status once with the checkoutID (after one time the checkoutID expires). To request the payment status a second time, please see this page

 

User authorization failed 800.900.300

When you query the transaction result, you get a 800.900.300 code.

{"result":{"code":"800.900.300","description":"user authorization failed"},"buildNumber":"82d393aad4390f43d567cfe15346f9e89bda7fae@2018-05-25 08:09:59 +0000","timestamp":"2018-05-28 07:47:02+0000","ndc":"577D442889CBE0BAB37802C38C0F8DA2.sbg-vm-tx01"}

Possible fix

  • You have entered non matching authentication.userId and authentication.password

 

Invalid or missing entity type

You want to load the widget and you see the text below.

Payment cannot be completed.
Please contact support with following information:
invalid or missing entity type
ndc: E1C3CC6D2A9B407EF1F712A3CB262C13.prod01-vm-tx05
timestamp: Mon, 28 May 2018 07:49:33 GMT

Possible fix

  • In step 1 you have probably used the live endpoint with test credentials (authentication.userId and authentication.password) or vice versa

 

checkoutId ... is invalid

Payment cannot be completed.
Please contact support with following information:
checkoutId ECABC8F625FA7B9FCA62BE620BE5D01A.sbg-vm-tx0 is invalid
ndc: 02f2b7ca10474cdda332f14feba3c53c
timestamp: Mon, 28 May 2018 08:22:12 GMT

Possible fix

  • The checkoutid is not entered correctly when calling the widget

 

Found 0 transactions instead of 1

Payment cannot be completed.
Please contact support with following information:
Found 0 transactions instead of 1
ndc: AAA1BF472A22EFDE34BAA4E6E42FC011.sbg-vm-tx02
timestamp: Thu, 29 Mar 2018 08:08:52 GMT

Possible fix

  • You are not using a valid registration id. The registration id should be the token that you received when the card was stored

 

Have more questions? Submit a request

Comments

Powered by Zendesk