Versions Compared

Old Version 9

changes.mady.by.user David Breihan

Saved on

compared with

New Version 10

changes.mady.by.user David Breihan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

For a more secure option, you can provide a S2S URL for completes and reconciliations/reversals.

...

Note

Note that we use the POST method when sending the S2S callback

...

Example URL

https://company.com/purespectrum/s2s?&transactionId=[SupplierSessionID]&memberId=[SupplierUserMemberID]&cpi=0.78&asr_s_hash=123abc456def91011xyz

...

Info

If you’ve added a Hashkey, this will return appended as “&asr_s_hash=”
Security and hashing will be covered in the next section of the documentation.

Reconciliation/Reversal Callback

In order to be notified once a buyer has reconciled one of your respondent’s transactions, you will need to enter postbacks for those use cases. You can define a Postback URL for the following 2 scenarios:

...

  • The CPI value

  • Session ID

  • Old status

  • New Status

...

Example URL

http://test.com/completetononcomplete?ps_rstatus=33&oldStatus=21&supSid=12345678&supCpi=1.20&ps_s_hash=123abc456def91011xyz

For more information on Hashing and Security, please click the following link:

Fusion: Security / IP Whitelisting